mcp-sympy

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Symbolic addition' implies a mathematical operation but reveals nothing about what the tool actually returns, whether it performs simplification, error handling, or any behavioral characteristics. The comma-separated format hint is minimal behavioral information.

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 extremely concise at just three words, which could be appropriate for a simple tool. However, it's arguably under-specified rather than efficiently concise. The information is front-loaded but lacks necessary detail.

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 1 parameter with 0% schema coverage, no annotations, but an output schema exists, the description is incomplete. It doesn't explain what 'symbolic' means, doesn't provide examples, and offers minimal guidance despite the tool existing in a complex mathematical ecosystem with many sibling tools. The output schema helps but doesn't compensate for the sparse description.

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 mentions 'comma-separated' which provides some format guidance for the 'terms' parameter, but doesn't explain what constitutes valid terms (symbols, numbers, expressions), whether parentheses are allowed, or any constraints. This adds minimal value beyond the bare 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 states 'Symbolic addition (comma-separated)' which provides a basic purpose (addition operation) and hints at parameter format. However, it's vague about what 'symbolic' means in this context and doesn't clearly distinguish from sibling tools like 'sympy_sum' or 'sympy_matrix_add' that might also perform addition 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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention sibling tools, doesn't specify use cases, and offers no context about prerequisites or when this specific addition tool is appropriate versus other mathematical operations in the extensive sibling list.

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