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. The description reveals nothing about what the tool does behaviorally - whether it's a constant, a constructor, a property, or an operation. It doesn't indicate if this is a read-only tool, what it returns, or how it interacts with mathematical expressions.

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 four words, this description is under-specified rather than efficiently informative. It fails to convey the tool's purpose or behavior, making it an example of harmful brevity where conciseness comes at the cost of essential information.

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 mathematical context with 100+ sibling tools and no annotations, the description is completely inadequate. While an output schema exists, the description fails to explain what this tool does, when to use it, or how it fits within the SymPy mathematical computation ecosystem. For a tool in a complex mathematical server, this minimal description leaves the agent guessing.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain parameters since there are none, and the schema fully documents this. The description doesn't add parameter information, but that's appropriate given the zero-parameter design.

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 'The set of real numbers' is a tautology that essentially restates the tool name 'sympy_reals' without specifying what the tool actually does. It doesn't indicate whether this tool creates, returns, operates on, or represents real numbers, nor does it distinguish this tool from its many siblings in the SymPy mathematical toolkit.

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. With 100+ sibling tools in the SymPy server including mathematical operations, set operations, and symbolic computation tools, the agent receives no indication of this tool's specific role or context within the mathematical toolkit.

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