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. 'Check ODE solution' implies a verification operation but reveals nothing about what the check entails, what constitutes a valid solution, what output to expect, error conditions, or computational characteristics. This is inadequate for a tool with 2 parameters and an output schema.

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 at just three words. While this represents under-specification rather than ideal conciseness, it contains no wasted words and is front-loaded with the core purpose. Every word earns its place, though more content would be beneficial.

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 verification tool with 2 parameters, 0% schema description coverage, no annotations, but with an output schema, the description is severely incomplete. While the output schema may document return values, the description fails to explain what the tool actually does, how to use it properly, or what the parameters mean. This leaves significant gaps for an agent trying to invoke the tool correctly.

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 0%, meaning neither 'eq' nor 'sol' parameters have descriptions in the schema. The tool description adds no information about what these parameters represent, their expected formats, or examples. For a mathematical tool checking ODE solutions, this leaves the agent guessing about proper input syntax and semantics.

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 'Check ODE solution' is a tautology that essentially restates the tool name 'sympy_checkodesol'. It specifies the verb 'check' and resource 'ODE solution', but doesn't clarify what checking entails or what type of ODEs are supported. It doesn't distinguish from siblings like 'sympy_classify_ode' or 'sympy_dsolve' which are related to ODE analysis.

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 when this verification tool should be used instead of solving ODEs with 'sympy_dsolve' or classifying them with 'sympy_classify_ode'. There's no context about prerequisites, expected inputs, or typical use cases.

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