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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the tool is read-only, whether it can handle symbolic simplification, what happens with invalid expressions, whether variables are substituted, or what the output format is. The description is too thin to convey the tool's behavior beyond the basic operation.

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 sentence that is reasonably concise and front-loads the core purpose. It could be slightly more structured by separating evaluation from simplification, but it is not bloated or redundant.

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 tool has 3 parameters, no annotations, and an output schema, the description is incomplete. It does not explain the simplify flag, the variables parameter, or the return value semantics. An agent would need to inspect the schema and possibly experiment to understand how to use this tool correctly.

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 description coverage is 0%, so the description must compensate for the three parameters. It explains the 'expression' parameter implicitly by describing what expressions are, but it does not explain the 'simplify' boolean or the 'variables' object at all. The description adds some meaning for the main parameter but leaves the other two undocumented.

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 states a specific verb ('Evaluate or simplify') and a clear resource ('mathematical expressions'), and lists supported operations (PEMDAS, sqrt, exp, log, sin, cos). It is distinguishable from siblings like solve_equation_system and verify_arithmetic_claim, though it does not explicitly name them.

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 usage for evaluating or simplifying math expressions, and the mention of PEMDAS and functions gives some context. However, it does not explicitly state when to prefer this tool over alternatives like solve_equation_system, verify_arithmetic_claim, or compute_number_theory, nor does it mention exclusions or prerequisites.

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