simplify_expression

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It only states a high-level operation without mentioning side effects, session handling, state changes, or return behavior, leaving the agent without safety or execution context.

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 sentence with no unnecessary words, which is concise in form. However, it is under-informative and does not earn its place by adding meaningful context beyond what the name already implies.

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 large number of sibling mathematical operation tools and the absence of annotations, the description is too sparse to understand the scope of 'simplify'. While an output schema exists, the description still fails to clarify what form of simplification is intended or how it differs from related operations.

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?

Both parameters ('expression' and 'session') are fully described in the schema, so the baseline is 3. The description adds no parameter-specific meaning beyond the schema, but the schema itself is sufficient.

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 'Simplify a mathematical expression' essentially restates the tool name 'simplify_expression', adding only the word 'mathematical'. It gives no detail on what kind of simplification is performed and does not distinguish from siblings like expand_expression or factor_expression.

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. There are no statements about when to choose simplification over expansion, factoring, or calculation, and no mention of exclusions or prerequisites.

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