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. It doesn't disclose behavioral traits such as whether it's a read-only computation, how it handles errors, or what the output looks like. The description is minimal and adds no context beyond the basic function name.

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 'Exponential function.', which is front-loaded and wastes no words. For a simple mathematical tool, this brevity is appropriate, though it may sacrifice 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 tool's simplicity (one parameter, high schema coverage, output schema exists), the description is minimally complete. However, it lacks context on behavior and usage, which could be helpful for an AI agent. The output schema likely covers return values, so the description doesn't need to explain those.

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 100%, with the parameter 'expr' documented as 'Expression'. The description doesn't add any meaning beyond this, such as examples of valid expressions or formatting details. With high schema coverage, the baseline score of 3 is appropriate as the schema handles parameter documentation adequately.

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 'Exponential function.' states the mathematical operation but is vague about its specific application within the SymPy context. It distinguishes from siblings by naming the exponential function, but doesn't clarify what it does with the input expression (e.g., compute e^expr, apply exp transformation). The purpose is identifiable but lacks specificity.

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_powsimp or sympy_expand. The description doesn't mention prerequisites, typical use cases, or comparisons with sibling tools, leaving the agent to 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.