MCP Math 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 mathematical domain and category, but does not specify error handling, input constraints (e.g., x > 0), or output format, leaving significant gaps for a mutation-free tool.

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 front-loaded with the core functionality, uses a single efficient sentence, and includes a parenthetical note for context without unnecessary elaboration, making it highly concise and well-structured.

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 low complexity and lack of annotations or output schema, the description is minimally adequate but incomplete. It covers the basic purpose and parameter semantics but omits important behavioral details like input domain restrictions or error conditions.

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?

The description adds meaning by clarifying that 'x' is the number for which the base-10 logarithm is calculated. However, with 0% schema description coverage and no additional details on parameter constraints or examples, it only partially compensates for the schema's lack of documentation.

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 explicitly states the tool's purpose with a specific verb ('calculate'), resource ('base-10 logarithm of a number'), and output ('Returns log₁₀(x)'), clearly distinguishing it from sibling tools like 'ln' or 'log2' that compute different logarithms.

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 for base-10 logarithm calculations but does not explicitly state when to use this tool versus alternatives like 'ln' or 'log2', nor does it provide any exclusions or prerequisites for its use.

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