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. 'Complex conjugate' gives no information about what the tool actually does behaviorally - whether it returns a symbolic expression, numeric value, or something else; whether it has side effects; what errors might occur; or any performance characteristics. This is completely inadequate for a tool with mathematical computation.

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 maximally concise at just two words. While this represents severe under-specification rather than ideal conciseness, from a pure length perspective it's extremely brief with zero wasted words. Every word (both of them) directly relates to the tool's mathematical concept.

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 that this is a mathematical computation tool with no annotations, 0% schema description coverage, but with an output schema present, the description is incomplete. The output schema will help with return values, but the description fails to explain what the tool does, when to use it, what the parameter means, or any behavioral context. For a tool in a large family of mathematical operations, this leaves critical gaps.

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 schema description coverage is 0%, meaning the single parameter 'expr' has no documentation in the schema. The description 'Complex conjugate' adds absolutely no information about what the 'expr' parameter should be - whether it's a mathematical expression string, a symbolic object, or something else. For a single parameter with zero schema documentation, the description fails completely to compensate.

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 'Complex conjugate' is a tautology that essentially restates the tool name 'sympy_conjugate'. It doesn't specify what action is performed (e.g., 'compute the complex conjugate of a symbolic expression') or what resource is involved. While it hints at mathematical functionality, it lacks the specific verb+resource clarity needed for an AI agent to understand what this tool actually does.

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 numerous sibling tools in the sympy family (like sympy_re, sympy_im, sympy_abs, sympy_as_real_imag), there's no indication of when complex conjugate computation is appropriate versus other complex number operations. No context, exclusions, or alternatives are mentioned.

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