solve_root

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description explains the bracket/guess strategy and angle_mode for trig functions, but does not disclose return value, failure behavior, or whether it finds all roots or just one.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description uses a compact labeled format ('When:', 'Params:', 'Example:') and contains only essential information, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, parameters, and an example. While it could include more about output or edge cases, the presence of an output schema and the simple nature of a numeric root solver make it sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides zero descriptions, but the description explains that expression is in x, bracket is a preferred interval, guess is an alternative, and angle_mode affects trig functions in f. The example demonstrates usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it solves for the numeric root of an infix expression f(x)=0. This distinguishes it from polynomial, linear, and inequality solvers among siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says 'When: numeric root of infix f(x)=0', providing a clear trigger for use. It also advises to prefer bracket over guess, but does not name alternative tools for other root types.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.