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. 'Horner form' reveals nothing about whether this is a read-only transformation, whether it modifies data, what permissions might be needed, or what the output looks like. For a mathematical transformation tool with zero annotation coverage, this is completely inadequate.

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 under-specification rather than effective conciseness. The description fails to communicate essential information and doesn't follow the principle of front-loading critical details. Every word should earn its place, but these two words provide almost no value.

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 transformation tool with 2 parameters, 0% schema coverage, no annotations, but with an output schema, the description is severely incomplete. While the output schema might help with return values, the description fails to explain what the tool does, when to use it, or how parameters work - leaving the agent with insufficient context to use the 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?

With 0% schema description coverage for both parameters (expr and variable), the description provides no information about what these parameters mean or how they should be used. 'Horner form' gives no hint about parameter roles, expected formats, or the relationship between expr and variable in the transformation.

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 'Horner form' is a tautology that restates the tool name without specifying what the tool does. It doesn't provide a verb-action or clarify what resource is being transformed. While the name suggests it performs Horner's method on expressions, the description adds no value beyond the name itself.

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 on when to use this tool versus alternatives. Given the many sibling tools for symbolic mathematics (like sympy_expand, sympy_factor, sympy_simplify), there's no indication of when Horner form is appropriate or what problems it solves compared to other transformation methods.

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