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. 'Fresnel C.' gives no information about what the tool does operationally (e.g., computes the Fresnel cosine integral), its input/output behavior, error handling, or computational characteristics. This leaves the agent with no understanding of how the tool behaves beyond its name.

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 ('Fresnel C.'), but this is under-specification rather than effective brevity. It lacks any structure or front-loaded information, failing to convey purpose or usage in a meaningful way. While short, it doesn't earn its place by providing 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 the complexity of a mathematical function tool with no annotations, 0% schema description coverage, and an output schema (which helps but isn't described), the description is completely inadequate. It doesn't explain what the tool computes, how to use it, or what to expect, leaving critical gaps for the agent to operate 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?

The input schema has 1 parameter with 0% description coverage, and the description 'Fresnel C.' adds no information about the parameter 'expr'. It doesn't explain what 'expr' should be (e.g., a mathematical expression, a numeric value, a symbolic variable), its format, or constraints. With low schema coverage and no compensation in the description, this is inadequate.

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 'Fresnel C.' is a tautology that merely restates the tool name without explaining what it does. It doesn't specify the verb (e.g., compute, evaluate, calculate) or the resource (e.g., the Fresnel C integral function), nor does it distinguish this from sibling tools like 'sympy_fresnels' which likely handles the related Fresnel S function. This provides minimal actionable information.

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. It doesn't mention sibling tools (e.g., 'sympy_fresnels' for the Fresnel S function), other mathematical functions in the sympy suite, or any context for application (e.g., optics, diffraction). The description is too sparse to imply usage scenarios.

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