simplify_expression

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

No annotations are provided, so the description carries the full burden. The input-to-output example does disclose the core behavior (a pure, deterministic symbolic rewrite returning a simplified form), but it says nothing about assumptions, domain restrictions, or whether simplification is canonical for a given input.

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?

A single front-loaded sentence with an inline example; nothing redundant and the essential information comes first.

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?

An output schema exists, so return values need no explanation, and for a one-parameter pure math function the description is nearly sufficient. It only falls short on routing guidance relative to the many sibling symbolic tools.

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?

Schema coverage is 0% and the single required parameter 'expression' is undocumented in the schema. The example ('sin(x)**2 + cos(x)**2') does demonstrate the expected string syntax, including the ** operator, which partially compensates, but format details such as variable names or accepted functions are left implicit.

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?

States a specific verb ('simplify') and resource ('symbolic expression'), with a concrete before/after example making the transformation unambiguous. It does not, however, distinguish itself from its close siblings expand_expression and factor_expression, which are also symbolic rewrites.

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 on when to choose this over expand_expression, factor_expression, or the other symbolic siblings. The example implies it is a canonicalizing rewrite, but there is no explicit when/when-not statement or named alternative.

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