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. 'Toggle evaluation globally' suggests this controls some system-wide setting, but doesn't explain what 'evaluation' entails, whether this affects subsequent operations, what the default state is, or what the output will be. For a tool that likely changes system behavior, this is critically insufficient.

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 three words. While it's under-specified, every word earns its place - 'toggle' indicates the action, 'evaluation' specifies what's being toggled, and 'globally' indicates scope. There's no wasted language or 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 that this is a configuration tool with no annotations, 0% schema description coverage, but with an output schema, the description is incomplete. It doesn't explain what 'evaluation' means in SymPy context, what the tool actually does behaviorally, or when to use it. The existence of an output schema helps, but the core functionality remains opaque for a tool that likely affects system state.

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 0% description coverage with one parameter 'flag' (boolean, default true). The description mentions 'toggle' which implies the boolean nature, but doesn't explain what true/false values mean ('enable evaluation' vs 'disable evaluation'). Since there's only one parameter and the schema provides the type and default, the description adds minimal but not zero value, meeting the baseline for 0 params.

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 'Toggle evaluation globally' is a tautology that essentially restates the tool name 'sympy_evaluate' without specifying what 'evaluation' means in the SymPy context. It doesn't distinguish this tool from its many siblings (e.g., sympy_evalf, sympy_simplify) that also involve evaluation operations. The purpose remains vague rather than specifying what resource or behavior is being toggled.

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 dozens of sibling tools for mathematical operations in SymPy, there's no indication of what 'global evaluation' means, when it should be enabled/disabled, or what tools might be alternatives. This leaves the agent with no usage context.

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