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. 'Natural logarithm.' gives no information about what the tool actually does behaviorally - whether it evaluates expressions symbolically or numerically, what format the output takes, error conditions, or computational characteristics. This is completely inadequate for a mathematical computation tool.

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 the description is brief with just two words, this represents under-specification rather than effective conciseness. The description fails to convey essential information about the tool's purpose and behavior. Every sentence should earn its place, but here the single phrase fails to provide meaningful content.

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 that this is a mathematical computation tool with no annotations, 1 parameter, and an output schema exists, the description is incomplete. While the output schema may document return values, the description should still explain what the tool does, its mathematical behavior, and how it differs from related tools. The current description provides none of this essential 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?

The input schema has 100% description coverage with the 'expr' parameter documented as 'Expression'. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in description.

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 'Natural logarithm.' is a tautology that restates the tool name 'sympy_log' without specifying what it does. It doesn't mention that this tool calculates the natural logarithm of a mathematical expression using the SymPy library, nor does it differentiate from sibling tools like sympy_log_base which handles logarithms with custom bases.

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 when to choose sympy_log over sympy_log_base for base-e calculations, or how it relates to other mathematical functions in the sibling list. There's no context about use cases or prerequisites.

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