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. It discloses the tool creates an HTML file (implied by 'producing an HTML comparison page' and 'saveTo' parameter), but doesn't mention permissions needed, rate limits, error conditions, or what happens if the file already exists. The behavioral context is minimal but not contradictory.

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?

Two sentences with zero waste. The first sentence states purpose and output, the second provides key usage guidance. Every word earns its place and the information is front-loaded appropriately.

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?

For a tool with 4 parameters, no annotations, and no output schema, the description is adequate but minimal. It covers the core purpose and basic usage but lacks details about behavioral traits, error handling, or output format beyond 'HTML comparison page'. The schema carries most of the parameter documentation burden.

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 100%, so the schema already documents all parameters thoroughly. The description adds some context about the {PARAM} placeholder usage and the exploration purpose, but doesn't provide additional syntax, format, or constraint details beyond what's in the schema descriptions.

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 ('Render a parameterized equation across a grid of values') and the output ('producing an HTML comparison page'). It distinguishes from siblings by focusing on parameter grid exploration rather than individual rendering or validation tasks.

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 ('Useful for exploring how changing coefficients affects formulas') that indicates when to use this tool. However, it doesn't explicitly mention when not to use it or name specific alternatives among the sibling tools.

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