simplify_expression

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It communicates that the tool simplifies expressions but does not explain whether it returns a simplified form, operates on symbolic expressions, or what happens with invalid or non-simplifiable inputs.

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 is a single concise sentence with no redundancy. It is front-loaded with the action and resource, though it could have used its brevity to add more useful context without becoming verbose.

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?

For a one-parameter tool this is simple in shape, but the overall context is incomplete: no input format guidance, no usage alternatives, and no behavioral detail. The presence of an output schema reduces the need to describe return values, but the description still leaves an agent guessing about how to correctly invoke the tool.

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 has 0% description coverage for the single parameter, and the description only repeats the notion of a 'mathematical expression' without specifying syntax, accepted formats (e.g., plain math vs. LaTeX), variable conventions, or constraints. The description fails to compensate for the lack of schema-level parameter documentation.

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 a specific action ('Simplifies'), a resource ('a mathematical expression'), and a method ('using algebraic identities'). It effectively distinguishes this from siblings like solve_equation or evaluate_expression, though it does not explicitly name a distinct sibling alternative.

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?

No guidance is given about when to use this tool versus alternatives such as evaluate_expression or step_by_step_algebra. There is no mention of prerequisites, input format expectations, or scenarios where simplification would or would not be appropriate.

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