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 the tool renders equations into an HTML page and saves it to a file, but doesn't describe what happens if the file path is invalid, whether it overwrites existing files, if there are rate limits, or what the output looks like (e.g., HTML structure). For a tool with file system interaction and no annotations, this is a significant gap.

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 concise with two sentences: one stating the purpose and another providing usage context. It's front-loaded with the core functionality, and every sentence adds value without redundancy. However, it could be slightly more structured by explicitly separating purpose from guidelines.

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 (rendering equations to HTML with file saving), no annotations, and no output schema, the description is incomplete. It covers the basic purpose and usage but lacks details on behavioral aspects like error handling, file overwriting, or output format. The schema handles parameters well, but the description should compensate for missing annotations and output information.

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 (title, equations, saveTo). The description adds minimal value by implying the tool handles 'collections' of equations, which aligns with the 'equations' array parameter, but doesn't provide additional semantics beyond what the schema specifies. Baseline 3 is appropriate when 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 tool's purpose: 'Render a collection of named equations into a single reference sheet HTML page.' It specifies the verb (render), resource (equations), and output format (HTML page). However, it doesn't explicitly differentiate from sibling tools like 'render_equation' (singular) or 'render_markdown_with_math', which might have overlapping functionality.

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 some usage context with 'Useful for creating equation cheat sheets or appendix summaries,' which implies when this tool is appropriate. However, it doesn't explicitly state when to use alternatives like 'render_equation' (for single equations) or 'render_markdown_with_math' (for markdown content), nor does it mention prerequisites or exclusions.

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