Symbolic Algebra MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden and does well by detailing what gets destroyed (clears all stored items) and what gets reinitialized (unit variables). It also mentions the return value (confirmation message). However, it doesn't address potential side effects like whether this affects ongoing computations or requires specific permissions.

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?

Perfectly structured with zero waste: first sentence states purpose, second enumerates what gets cleared, third specifies reinitialization, fourth provides usage timing, fifth describes return value. Every sentence adds essential information without redundancy.

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 this is a state management tool with 0 parameters and no output schema, the description provides complete context: what it does, what gets affected, when to use it, and what it returns. No annotations exist to supplement this information, yet the description stands adequately on its own.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on the tool's behavior and usage context.

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 clearly states the specific action ('Resets the state') and the resource ('SymPy MCP server'), listing exactly what gets cleared (variables, functions, expressions, metrics, tensors, coordinate systems, expression counter) and what gets reinitialized (unit variables). It distinguishes itself from all sibling tools which perform mathematical operations rather than system maintenance.

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?

Explicitly states when to use this tool: 'Runs after all tool calls for a given computation are done to reset the state for the next computation.' This provides clear context about its timing and purpose relative to other tools, with no ambiguity about when it should be invoked.

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