Simple Remote MCP Server

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

No annotations are provided, so the description carries full burden. It states what the tool does (addition) and the return value, but doesn't disclose any behavioral traits like error handling, precision limits, overflow behavior, or performance characteristics that would be important for an arithmetic operation.

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 appropriately sized with clear sections (Args, Returns). The main purpose is stated upfront, and each sentence serves a clear purpose. The structure could be slightly improved by integrating the parameter descriptions more naturally rather than as separate labeled sections.

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 simplicity (2 integer parameters, no annotations, but has output schema), the description is reasonably complete. It explains what the tool does, what parameters mean, and what it returns. The output schema existence means the description doesn't need to detail return format, making this adequate for this simple arithmetic function.

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, the description compensates by clearly explaining both parameters ('First number' and 'Second number'). While it doesn't provide format details beyond what the schema already shows (integers), it adds meaningful semantic context for each parameter.

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 ('Add two numbers together') and identifies the resource (numbers). It distinguishes from the sibling tool 'random_number' by focusing on arithmetic addition rather than random generation.

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 arithmetic addition but doesn't explicitly state when to use this tool versus alternatives. No guidance is provided about when not to use it or what other tools might be appropriate for different mathematical operations.

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