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 offers no details. It does not indicate whether this is a read-only analysis, if it modifies data, what permissions are needed, or any rate limits. The lack of information makes it impossible for an agent to understand the tool's behavior beyond its 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?

While concise with only two words, the description is under-specified rather than efficiently informative. It fails to front-load essential details, offering no structure or elaboration to aid understanding, making it ineffective despite its brevity.

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 complexity of ODE classification, two undocumented parameters, and no annotations, the description is incomplete. Although an output schema exists (which might cover return values), the description does not compensate for the lack of parameter explanations or behavioral context, leaving significant gaps for agent usage.

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 neither parameter ('eq' and 'func') is documented in the schema. The description adds no semantic information about these parameters, such as what 'eq' and 'func' represent, their expected formats, or examples. This leaves both parameters entirely unexplained.

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 'Classify ODE' is a tautology that merely restates the tool name 'sympy_classify_ode' without adding meaningful context. It lacks a specific verb and resource details, failing to clarify what classification entails or what distinguishes it from sibling tools like 'sympy_dsolve' (which solves ODEs) or 'sympy_checkodesol' (which verifies solutions).

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. The description does not mention any context, prerequisites, or comparisons to sibling tools, leaving the agent with no information to make an informed choice among related ODE tools in the server.

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