mcp-sympy

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Create' implies a write operation, the description doesn't specify whether this creates persistent symbols, what happens if symbols already exist, or any permissions/rate limits. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 perfectly concise at three words ('Create symbolic variables'), front-loading the essential action and resource with zero wasted language. Every word earns its place in communicating the core functionality.

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 simple single parameter with full schema coverage and the existence of an output schema (which means return values are documented elsewhere), the description is minimally adequate. However, with no annotations and many similar sibling tools, it could benefit from more context about when and how to use it 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?

The input schema has 100% description coverage, with the 'names' parameter clearly documented as 'Comma-separated symbol names (e.g., "x, y, z")'. The description doesn't add any parameter information beyond what the schema provides, so it meets the baseline of 3 when schema coverage is complete.

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 symbolic variables' clearly states the verb ('Create') and resource ('symbolic variables'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'sympy_symbol' or 'sympy_symbols_create' that appear to have similar functionality, missing an opportunity for differentiation.

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. With many sibling tools in the SymPy server (including 'sympy_symbol' and 'sympy_symbols_create'), there's no indication of when this specific tool is appropriate, leaving the agent to guess based on naming alone.

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