UpMath MCP Server

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. It mentions rendering to HTML with embedded SVG equations, which hints at output format, but doesn't cover critical aspects like whether this is a read-only operation, potential side effects (e.g., file creation via 'saveTo'), performance considerations, or error handling. For a tool with parameters and no annotations, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence that front-loads the core action and output, with no wasted words. It directly communicates the tool's function without unnecessary elaboration, making it easy to parse and understand quickly.

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 has 2 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain the return value (e.g., HTML string or file path), error conditions, or how the 'saveTo' parameter affects behavior (e.g., whether it saves to disk or returns a file reference). For a rendering tool with potential side effects, more context is needed to use it effectively.

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%, with clear descriptions for both parameters: 'markdown' as input content and 'saveTo' as an optional file path. The description adds minimal value beyond the schema, only implying that LaTeX equations should be in $$...$$ format, which is somewhat redundant with the schema's description. Baseline 3 is appropriate since the schema does the heavy lifting.

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 verb 'Render' and the resource 'markdown containing $$...$$ LaTeX to HTML with embedded SVG equations', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'render_equation' or 'render_paper', which likely handle similar content but with different scopes or outputs.

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 such as 'render_equation' for standalone equations or 'render_paper' for full documents. It implies usage for markdown with LaTeX equations but lacks explicit when/when-not instructions or prerequisites, leaving the agent to infer context from tool names alone.

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