MCP Server Sample

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

No annotations provided, so description carries full burden. Fails to disclose return value (the sum), error conditions (overflow), or whether the operation is pure/idempotent. Minimal behavioral disclosure.

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?

Three-word description with zero redundancy. Front-loaded and appropriately sized for the trivial complexity of the operation. No waste.

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 extreme simplicity (2 primitive params) and no output schema, the description is minimally viable but should ideally specify the return value (sum) since no output schema exists to document it. Just meets threshold for a basic arithmetic utility.

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?

With 0% schema description coverage (params lack descriptions beyond titles 'A'/'B'), the description provides minimal semantic value by identifying the parameters as 'two numbers'. However, it does not clarify roles, constraints, or formats beyond the schema types.

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?

States specific verb (Add) and resource (two numbers) clearly. Lacks sibling differentiation, but there are no siblings present. Extremely terse but sufficient for this trivial operation.

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?

Provides no guidance on when to use versus alternatives, prerequisites, or contextual requirements. Merely states the operation without any conditional logic or workflow positioning.

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