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 states the tool simplifies rational expressions but does not explain what 'simplify' entails (e.g., reducing fractions, combining terms), potential side effects, error conditions, or output format. This leaves significant gaps in understanding the tool's behavior for an agent.

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, efficient sentence with no wasted words. It is front-loaded with the core purpose, making it easy for an agent to quickly understand the tool's function without unnecessary elaboration.

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 tool's moderate complexity (mathematical simplification), the presence of an output schema (which likely defines the result structure), and high schema coverage, the description is minimally adequate. However, it lacks details on behavioral aspects and usage context, which are important for an agent to operate the tool effectively in a crowded namespace of sibling tools.

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 'String rational expression'. The description does not add any additional meaning beyond this, such as examples of valid expressions or formatting requirements. Since the schema provides adequate coverage, the baseline score of 3 is appropriate.

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 'Simplify rational expressions' clearly states the tool's function with a specific verb ('Simplify') and resource type ('rational expressions'). It distinguishes itself from generic simplification tools like 'sympy_simplify' by specifying the type of expression, though it doesn't explicitly differentiate from similar siblings like 'sympy_cancel' or 'sympy_together' which also handle rational expressions.

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 many sibling tools for mathematical operations (e.g., 'sympy_simplify' for general simplification, 'sympy_cancel' for canceling common factors), there is no indication of specific use cases, prerequisites, or comparisons to help an agent choose appropriately.

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