Improved tool documentation, explicit field for error, and error filtering

What feature would you like to be added?

1. Documentation currently describes only happy paths for tools. It is unclear how to deal with errors in tools. There is no mention that you can simply raise an exception.
2. The FunctionExecutionResultMessage should have a field indicating that an error was raised (Somewhat related #4725 )
3. An option to catch only specific errors with the option to stop for others

Why is this needed?

1. Avoids that everyone has to read the code
2. Anthropic models have an explicit field to indicate tool errors
3. Some exceptions indicate serious issues that make it useless to continue. At that point I'd like to stop.