UpMath MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: caching behavior ('skips re-rendering unchanged equations'), performance benefit ('Much faster'), and session persistence ('Cache persists within the MCP session'). It doesn't cover aspects like error handling or rate limits, but provides substantial operational context.

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 highly concise and front-loaded: three sentences with zero waste. The first sentence states the core purpose, the second explains the benefit, and the third clarifies cache scope—each earning its place by adding distinct value.

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 (3 parameters, no output schema, no annotations), the description is largely complete. It covers purpose, usage context, and behavioral traits like caching. However, it lacks details on return values (e.g., what the tool outputs) and error cases, which are notable gaps for a rendering tool.

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?

Schema description coverage is 67% (2 of 3 parameters have descriptions). The description adds no specific parameter semantics beyond what the schema provides—it doesn't explain 'equations', 'format', or 'outputDir' further. Since coverage is moderate (>50%), the baseline score of 3 is appropriate, as the schema does most of the work without description compensation.

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 tool's purpose: 'Render multiple equations with caching — skips re-rendering unchanged equations.' It specifies the verb ('render'), resource ('multiple equations'), and key behavior ('with caching'), distinguishing it from siblings like 'render_batch' (which likely lacks caching) and 'render_equation' (which renders single equations).

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 clear context for when to use this tool: 'Much faster for iterative editing.' This implies it's optimal for scenarios where equations are edited incrementally. However, it doesn't explicitly state when not to use it or name alternatives (e.g., 'render_batch' for non-iterative cases), which prevents a perfect score.

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