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. It mentions the tool's function but does not disclose behavioral traits such as whether it modifies the input file, requires specific file permissions, handles errors, or has performance considerations. The description is functional but lacks 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 two sentences, front-loaded with the core functionality and followed by a practical use case. Every sentence earns its place without redundancy or unnecessary elaboration, making it efficient and easy to understand.

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 no annotations and no output schema, the description adequately covers the tool's purpose but lacks details on behavior, error handling, or output format specifics. It is complete enough for basic understanding but insufficient for full operational guidance without relying on the schema for parameters.

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 does not add meaning beyond the schema, as it does not explain parameter interactions, default behaviors, or usage examples. 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 specific action ('Extract all mathematical notation from a markdown file and generate a formatted notation table') and distinguishes it from siblings by focusing on notation extraction rather than rendering, validation, or other document processing tasks. It explicitly mentions the output components (symbol, meaning, first appearance) and practical use case ('creating a Notation section in a paper').

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 ('Useful for creating a Notation section in a paper') but does not explicitly state when to use this tool versus alternatives like 'scan_document_math' or 'validate_equations'. It provides a general purpose but lacks specific guidance on prerequisites or exclusions.

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