simplify_expression

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions that the tool produces multiple forms (simplified, factored, expanded), but it does not explain whether these are returned together, the order, error behavior for invalid expressions, or any side effects. This is insufficient for a tool with no structured annotation support.

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 short phrase with no redundant words, which is concise. However, it is under-specified; it could include more useful detail without becoming verbose. It is front-loaded in the sense that the key term 'simplified' appears first, but the lack of structure (no verb, no examples) limits its value.

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?

There is no output schema, so the description should explain the return value in detail. It mentions three forms but does not specify the data structure, how multiple forms are packaged, or how the input expression should be formatted. For a tool with one parameter and no annotations, this is incomplete.

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 one parameter (expr) with 0% description coverage, and the description does not compensate by explaining what expr should contain or its expected format. The only hint is the word 'expression' in the description, which is too vague to guide the agent in constructing valid input.

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 identifies the tool's output—simplified, factored, and expanded forms—which clearly indicates a simplification tool and distinguishes it from siblings like solve_expression or evaluate_expression. However, it lacks an explicit verb (e.g., 'Returns') and could be more direct about the operation.

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 provided on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or comparisons with sibling tools like algebraic_equiv or evaluate_expression. The intended use is only implied by the name and output description.

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