mcp-sympy

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Fresnel S.' gives no information about what the tool actually does - whether it computes, simplifies, evaluates, or performs some other operation on Fresnel S functions. It doesn't describe input/output behavior, error conditions, or any computational characteristics.

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 at just two words, but this represents under-specification rather than effective brevity. While it's technically front-loaded (the entire description is just two words), it fails to provide meaningful information, making the conciseness ineffective rather than efficient.

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?

For a mathematical computation tool with 1 parameter, 0% schema coverage, no annotations, and a complex sibling set, the description is completely inadequate. While an output schema exists, the description doesn't explain what the tool does, what the parameter means, or how it relates to mathematical operations. It provides essentially no useful context.

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?

Schema description coverage is 0%, meaning the single parameter 'expr' is completely undocumented in the schema. The description 'Fresnel S.' provides no information about what the parameter represents, what format it should be in, or what kind of expression is expected. This leaves the parameter semantics entirely unspecified.

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 S.' is a tautology that restates the tool name without explaining what it does. It doesn't specify the action (e.g., compute, evaluate, simplify) or what resource it operates on, making the purpose unclear. Compared to siblings like sympy_sin or sympy_integrate that clearly indicate mathematical functions, this provides minimal 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the mathematical context of Fresnel S functions, how it differs from related tools like sympy_fresnelc (a sibling tool), or any prerequisites for usage. There's complete absence of usage context.

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