UpMath MCP Server

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

With no annotations provided, the description carries full burden. It discloses the service provider (UpMath) and the two behavioral outcomes (returns SVG markup or saves to file), which is useful. However, it doesn't mention rate limits, authentication needs, error conditions, or whether the operation is idempotent - significant gaps for a tool with external dependencies.

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 concise sentences with zero waste. The first sentence states the core functionality, and the second explains the two possible outcomes. Every word earns its place, and the most important information is front-loaded.

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 3 parameters, no annotations, and no output schema, the description is adequate but incomplete. It covers the basic purpose and outcomes but lacks information about return values (beyond 'SVG markup'), error handling, performance characteristics, or integration details with UpMath service.

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 well. The description adds value by clarifying the relationship between format and saveTo - that format determines output type while saveTo specifies file storage. This semantic context goes beyond the schema's individual parameter 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 LaTeX equation'), the resource ('to SVG or PNG'), and the method ('via UpMath'). It distinguishes from siblings by focusing on single equation rendering rather than batch operations, diagrams, or other document types mentioned in the sibling list.

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 implies usage context by specifying 'LaTeX equation' and output formats, but doesn't explicitly state when to use this versus alternatives like render_batch, render_equation_sheet, or render_markdown_with_math. No explicit when-not-to-use guidance or prerequisite information is provided.

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