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. It states what the tool does but doesn't describe how it behaves: whether it returns a simplified string, handles errors for invalid input, preserves original formatting, or has any side effects. For a computational tool with zero annotation coverage, this leaves significant gaps in understanding its operational characteristics.

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, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable. Every word earns its place by directly contributing to the tool's purpose without redundancy or fluff.

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 moderate complexity (mathematical expression manipulation), the description is minimally adequate. The schema fully documents the single parameter, and an output schema exists (though not shown), reducing the need to describe return values. However, with no annotations and many sibling tools, the description lacks context on usage scenarios and behavioral details, leaving room for improvement.

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 'expr' parameter documented as 'String rational expression'. The description adds no additional parameter semantics beyond this, such as examples of valid expressions or formatting requirements. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, though the description doesn't compensate with extra context.

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 'Cancel common factors in rational expression' clearly states the verb ('Cancel') and resource ('common factors in rational expression'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like sympy_simplify or sympy_ratsimp that might also simplify expressions, leaving some ambiguity about when this specific cancellation operation is preferred.

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 for expression manipulation (e.g., sympy_simplify, sympy_factor, sympy_ratsimp), there's no indication of whether this is for specific types of rational expressions, preprocessing steps, or other contexts. The agent must infer usage from the tool name alone.

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