mcp-sympy

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 states the action ('Create') but doesn't explain what happens after creation—for example, whether the set is mutable, how it's stored, or if there are limitations on element types. This leaves significant gaps for an agent to understand the tool's behavior.

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, direct sentence with no wasted words. It's front-loaded and efficiently communicates the core action, making it easy to parse quickly without unnecessary elaboration.

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's simplicity (one parameter, high schema coverage, and an output schema exists), the description is minimally adequate. However, without annotations and with sibling tools that create similar objects, it lacks context about differentiation and behavioral details, making it incomplete for optimal agent use.

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?

The input schema has 100% description coverage, with the 'elements' parameter documented as 'Comma-separated elements'. The description doesn't add any meaning beyond this, such as examples or constraints on element formatting. With high schema coverage, the baseline score of 3 is appropriate, as the schema adequately defines the parameter.

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 'Create a finite set' clearly states the verb ('Create') and resource ('finite set'), making the purpose understandable. However, it doesn't differentiate from sibling tools like sympy_emptyset or sympy_universalset, which also create set-like objects, leaving room for ambiguity about when to choose this specific tool.

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. The description lacks context about prerequisites, such as whether elements must be symbolic expressions or can be numeric, and doesn't mention sibling tools like sympy_interval or sympy_product_set that might be relevant for different set types.

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