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 transparency. It only states the output forms and does not disclose whether all three forms are returned together, how symbolic expressions are handled, or any limitations. This is insufficient for a tool that likely has subtle symbolic computation behavior.

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, which is concise and front-loaded. However, it is a noun phrase rather than a complete sentence and could be more informative while remaining brief. There is no wasted text, but the structure is minimal.

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?

Given the absence of annotations, a 0% schema description coverage for parameters, and the presence of multiple math-related sibling tools, this description is too sparse. It does not explain the expected expression syntax, whether multiple forms are returned simultaneously, or how it differs from similar tools. The output schema exists, but that does not compensate for the lack of usage context.

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 single parameter 'expr' is of type string, but the schema provides no description and the tool description simply says 'an expression' without adding syntax, variable conventions, or examples. This adds little value beyond the parameter name itself.

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 the tool produces simplified, factored, and expanded forms of an expression, which specifies the resource and the type of output. It broadly distinguishes from sibling tools like evaluate_expression or solve_expression, though it lacks an explicit verb such as 'computes' or 'returns'.

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?

The description implies the tool is used when simplification, factoring, or expansion is desired, but it provides no explicit guidance on when to use it versus alternatives like evaluate_expression or algebraic_equiv. There are no exclusions or alternative tools mentioned.

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