mcp-sympy

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. 'Image set.' doesn't indicate whether this is a read or write operation, what permissions might be needed, what side effects exist, or what the output looks like. For a mathematical tool with 2 required parameters, this leaves critical behavioral aspects completely undocumented.

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?

While technically concise with just two words, this is an example of harmful under-specification rather than effective brevity. The description doesn't contain enough substance to be useful - it's not front-loaded with essential information, and the single phrase doesn't earn its place by providing any meaningful guidance.

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 tool with 2 required parameters, 0% schema description coverage, no annotations, and numerous sibling tools, the description is completely inadequate. While an output schema exists (which might help with return values), the description fails to explain what the tool does, when to use it, what the parameters mean, or any behavioral characteristics - making it impossible for an AI agent to use this tool effectively.

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 for both parameters (expr and variable), and the tool description provides no information about what these parameters mean or how they should be used. The description 'Image set.' doesn't mention parameters at all, leaving the AI agent with no understanding of what inputs are expected or their semantic purpose.

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 'Image set.' is a tautology that merely restates the tool name without adding any meaningful information about what the tool does. It doesn't specify what mathematical operation 'image set' refers to, what resources it operates on, or how it differs from sibling tools like sympy_solveset or sympy_finiteset. This provides no actionable guidance to an AI agent.

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 absolutely no guidance about when to use this tool versus alternatives. There's no mention of appropriate contexts, prerequisites, or comparisons to sibling tools like sympy_solveset or sympy_interval that might handle related mathematical operations. An AI agent would have no basis for selecting this tool over others.

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