mcp-sympy

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to mention whether this is a read-only or mutating operation, what the output entails, or any constraints like error handling. The phrase 'comma-separated' hints at input format but doesn't explain behavior beyond that.

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 with a single phrase, which is front-loaded and wastes no words. However, it borders on under-specification rather than effective brevity, as it lacks necessary detail for clarity.

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 complexity of symbolic math operations, no annotations, and an output schema (which isn't detailed in the context), the description is incomplete. It doesn't address key aspects like input format details, output expectations, or how it integrates with other SymPy tools, making it inadequate for informed 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 1 parameter with 0% description coverage, and the description adds minimal semantics by noting 'comma-separated' for the 'factors' parameter. However, it doesn't explain what 'factors' represents (e.g., symbolic expressions, numbers), leaving significant gaps in 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 'Symbolic multiplication (comma-separated)' restates the tool name 'sympy_symbolic_mul' with minimal elaboration, making it tautological. It mentions 'comma-separated' but doesn't clarify what is being multiplied or how this differs from other symbolic operations like 'sympy_symbolic_add' or 'sympy_product'.

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 like 'sympy_product' or 'sympy_mul' (if present). The description lacks context about its specific role among many sibling tools, offering no explicit or implied usage scenarios.

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