mcp-sympy

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('solve') without detailing traits like whether it returns symbolic solutions, handles initial/boundary conditions, supports specific ODE types, or has limitations. This leaves critical behavioral aspects 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 a single, efficient sentence with no wasted words. It is front-loaded and directly states the tool's purpose without unnecessary elaboration, making it highly concise and well-structured.

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 solving ODEs, no annotations, and 0% schema coverage, the description is insufficient. While an output schema exists, the description doesn't address behavioral traits, parameter meanings, or usage context, leaving significant gaps for effective tool invocation.

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 input schema has 2 parameters with 0% description coverage, and the tool description does not explain what 'eq' (the differential equation) or 'func' (the function to solve for) represent. It fails to compensate for the lack of schema documentation, leaving parameters semantically undefined.

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 'Solve ordinary differential equation' clearly states the tool's function with a specific verb ('solve') and resource type ('ordinary differential equation'), distinguishing it from siblings like 'sympy_solve' for algebraic equations. However, it doesn't specify whether it solves symbolically or numerically, or what form the solution takes, making it somewhat vague.

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_solve' for algebraic equations or 'sympy_nsolve' for numerical solutions. The description lacks context about prerequisites, such as needing a properly formatted ODE, or exclusions, like unsupported equation types.

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