intro

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

No annotations are provided, so the description carries full burden. It mentions 'stores it,' implying state mutation, but doesn't disclose behavioral traits like persistence scope, side effects, error conditions, or interaction with other tools (e.g., 'reset_state'). For a state-modifying tool, this is a significant gap in transparency.

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 appropriately sized with two sentences. The first sentence front-loads the core purpose, and the second adds parameter context without redundancy. It avoids unnecessary words, though it could be slightly more structured (e.g., separating purpose from parameter details).

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 annotations, 0% schema coverage, no output schema, and a state-modifying tool, the description is incomplete. It lacks details on behavioral traits, usage context, parameter constraints, and expected outcomes. For a tool that modifies sympy state, this leaves significant gaps for an AI agent to operate effectively.

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. It adds some meaning by explaining that parameters include 'a variable name and a list of positive and negative assumptions,' which clarifies the purpose of 'pos_assumptions' and 'neg_assumptions.' However, it doesn't detail assumption semantics, constraints, or examples, leaving gaps in parameter understanding.

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's purpose: 'Introduces a sympy variable with specified assumptions and stores it.' This specifies the verb ('introduces'), resource ('sympy variable'), and action ('stores it'). However, it doesn't differentiate from sibling tools like 'intro_many' or 'introduce_expression', which appear related.

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 no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'intro_many' (likely for multiple variables) or 'introduce_expression', nor does it specify prerequisites or context for usage. The second sentence only restates parameter information.

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