evaluate_expression

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

No annotations are provided, so the description carries full burden. It doesn't disclose whether the tool requires a symbolic math syntax (e.g., SymPy-like), whether it can throw errors for invalid expressions, or what edge cases behave like. The phrase 'evaluate or simplify' is ambiguous about what the output format is.

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 short and front-loaded with the purpose and examples. It does not waste words. However, it could be slightly more structured to mention syntax or limitations.

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?

With no annotations, no output schema, and no parameter details, the description is minimal. For a tool that performs symbolic math, the agent would need to know supported functions, syntax, and error behavior. The examples help but are insufficient for anything beyond trivial usage (e.g., how to use 'integrate' vs 'solve'). In comparison to sibling tools, it's 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?

Schema coverage is 0% (no description for the 'expression' parameter), and there is only one parameter. The description's examples ('integrate(x**2, x)', 'sqrt(144) + 2**10') give some semantic hint about the expected syntax, but they don't fully document the language or grammar of expressions. Since there's only one param, the burden is moderate; baseline with 0% coverage is compensation but examples partially cover it.

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 resource ('a math expression'), and gives concrete examples. However, it doesn't clearly distinguish from sibling tools like calc_exact, simplify_expression, or solve_expression, all of which perform related mathematical operations.

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 gives no guidance on when to use this tool versus siblings like calc_exact, simplify_expression, or solve_expression. It also doesn't specify input format requirements beyond the example, leaving the agent to guess.

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