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 set of complex numbers,' which implies a read-only operation but does not clarify if it returns a symbolic representation, a data structure, or something else. It lacks details on output format, error conditions, or any behavioral traits beyond the minimal implication.

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 sentence 'The set of complex numbers,' which is concise but under-specified rather than efficiently informative. It lacks front-loaded action or context, making it too brief to be truly helpful, though it avoids unnecessary verbosity.

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 mathematical tools and the presence of an output schema, the description is incomplete. It fails to explain what the tool returns or how it interacts with other SymPy operations, leaving significant gaps in understanding its role and behavior despite the structured data support.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add any parameter information, which is acceptable here since there are no parameters to describe, aligning with the baseline for zero parameters.

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 complex numbers' is a tautology that restates the tool name 'sympy_complexes' without specifying what the tool does. It lacks a clear verb or action, failing to distinguish this tool from its many siblings in the SymPy server, which perform various mathematical operations.

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. With numerous sibling tools like sympy_reals, sympy_integers, and sympy_rational, there is no indication of context, prerequisites, or comparisons to help an agent decide 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.