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

The description discloses that it performs exact symbolic computation with JSON ASTs and arbitrary-precision evaluation, and mentions numerical verification. No annotations are provided, so the description carries the full burden, and it adequately covers key behavioral traits.

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 very concise (two sentences plus an example), front-loaded with the main purpose, and every sentence adds value.

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 no output schema, the description provides sufficient context for a symbolic math tool, including an example and mention of verification. It could be more explicit about return values, but the complexity is well-covered.

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 are described in the schema (100% coverage), and the description adds meaning by explaining that spec is a structured problem and giving an example with operation='integrate'. This enhances understanding beyond the schema.

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 it is for exact symbolic computation using SymPy, listing specific operations like simplify, differentiate, integrate, etc. It distinguishes itself from sibling tools like numerical or chemistry by focusing on symbolic math.

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 provides clear usage guidance: pass an operation and spec, with an example of the spec format. It mentions verification and cost but does not explicitly state when not to use or compare with alternatives.

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