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. 'Logical NOT.' does not reveal any behavioral traits—such as whether it's a read-only operation, if it has side effects, performance considerations, or error handling. For a tool with no annotation coverage, this lack of information is a significant gap.

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 'Logical NOT.' is extremely concise with no wasted words. It is front-loaded and to the point, making it easy to parse quickly. Every word earns its place, though it may be overly brief for clarity purposes.

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 logical operations and the presence of an output schema, the description is incomplete. It lacks context on usage, behavioral traits, and differentiation from siblings. While the output schema may cover return values, the description fails to provide enough information for an agent to understand when and how to use this tool effectively, especially with no annotations.

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 clearly documented as a 'Boolean expression'. The description does not add any meaning beyond what the schema provides, as it mentions no parameters. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema adequately handles parameter documentation.

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 'Logical NOT.' is a tautology that essentially restates the tool name 'sympy_Not'. It does not specify what resource it operates on (e.g., a Boolean expression) or provide any distinguishing context from its many siblings, such as sympy_And, sympy_Or, or sympy_Xor. While it indicates a logical operation, it lacks the specificity needed for clear differentiation.

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 numerous sibling tools like sympy_And, sympy_Or, and sympy_Xor, there is no indication of context, prerequisites, or exclusions. This leaves the agent without any usage instructions, making it challenging to select the correct tool in practice.

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