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 set of integers' implies it might return or represent integers, but it doesn't specify whether this is a read-only operation, what it returns (e.g., a symbolic set object), or any behavioral traits like side effects or performance. For a tool with zero annotation coverage, this is insufficient to inform the agent about how the tool behaves.

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 with a single three-word phrase, 'The set of integers.' While it lacks substance, it is not verbose or poorly structured—it's front-loaded and wastes no words, earning full marks for conciseness despite its inadequacy in other dimensions.

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 tool's complexity (likely low, as it has no parameters and an output schema exists), the description is incomplete. It doesn't explain what the tool does, when to use it, or what it returns, even though an output schema might cover return values. With no annotations and minimal description, it fails to provide enough context for effective tool selection and 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 tool has 0 parameters with 100% schema description coverage, so the input schema fully documents the lack of parameters. The description doesn't add any parameter information, but since there are no parameters to explain, a baseline score of 4 is appropriate as the schema already handles this completely.

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 integers' is a tautology that merely restates the tool name 'sympy_integers' without specifying any action or purpose. It doesn't indicate what this tool does (e.g., create, return, or operate on integers), nor does it differentiate from sibling tools like sympy_naturals or sympy_rationals. This fails to communicate the tool's function beyond its name.

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 any context, prerequisites, or comparisons to sibling tools (e.g., sympy_naturals for natural numbers or sympy_rationals for rational numbers). Without any usage instructions, an agent cannot determine when this tool is appropriate.

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