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. 'Hyperbolic tangent' gives no information about what the tool actually does operationally - whether it evaluates, simplifies, differentiates, or performs some other mathematical operation on the expression. It doesn't mention that this is a symbolic mathematics function within the SymPy system.

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 two words, this represents under-specification rather than effective conciseness. The description fails to provide any meaningful information about the tool's purpose or usage, making it inefficient despite its brevity.

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 function tool with no annotations, the description is completely inadequate. It doesn't explain what hyperbolic tangent means mathematically, what the tool does with the expression parameter, or what type of output to expect (though an output schema exists). Given the complexity of mathematical operations and the rich sibling tool ecosystem, this 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 schema description coverage is 100% with the single parameter 'expr' documented as 'Expression'. The description adds no additional parameter information beyond what the schema provides. With high schema coverage and only one parameter, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 'Hyperbolic tangent' is a tautology that restates the tool name 'sympy_tanh' without specifying what the tool does. It doesn't mention that this is a mathematical function that computes the hyperbolic tangent of an expression, nor does it distinguish this from sibling tools like sympy_tan (regular tangent) or sympy_sinh/cosh (other hyperbolic functions).

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 zero guidance on when to use this tool versus alternatives. It doesn't mention that this is for hyperbolic tangent calculations specifically, nor does it reference any of the many sibling mathematical functions in the SymPy toolkit that serve different purposes.

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