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. 'Create Wild function' gives no information about what the tool returns, whether it's idempotent, what happens with invalid inputs, or any side effects. For a tool that creates symbolic entities, this leaves critical behavioral aspects completely unspecified.

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 three words. While this conciseness comes at the expense of completeness, there's no wasted language or unnecessary elaboration - every word directly addresses the tool's function.

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?

For a tool that creates symbolic mathematical entities with one parameter and no annotations, the description is completely inadequate. It doesn't explain what Wild functions are, how they're used in SymPy, what the output looks like (even with an output schema, some context would help), or provide any meaningful guidance for an AI agent.

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 has 0% description coverage, with one undocumented parameter 'name'. The description provides no information about what this parameter represents, what format it should take, or what constraints apply. It doesn't even mention that a parameter is required, leaving the agent with no semantic understanding 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 'Create Wild function' is a tautology that restates the tool name 'sympy_WildFunction' without adding meaningful context. It doesn't explain what a Wild function is in SymPy terms or how it differs from regular functions, nor does it distinguish this tool from sibling tools like 'sympy_Wild' or 'sympy_symbol' that might create other symbolic entities.

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. It doesn't mention typical use cases for Wild functions (e.g., pattern matching in symbolic expressions), prerequisites, or relationships to sibling tools like 'sympy_match' or 'sympy_Wild' that might be relevant in the SymPy ecosystem.

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