addSum two integers to get the total. Provide the first and second numbers to receive the result.
Add two numbers together.
| Name | Required | Description | Default |
|---|---|---|---|
| a | Yes | First number | |
| b | Yes | Second number |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.5.2Input schema / additionalPropertiesAdded value: +falseInput schema / properties / a / descriptionAdded value: +"First number"Input schema / properties / b / descriptionAdded value: +"Second number"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description clearly states the operation and implies the return value (the sum). No side effects or edge cases are mentioned, but none are expected for a pure arithmetic function.
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 a single concise sentence with no redundant information.
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?
For a simple two-integer addition function, the description provides sufficient information for the agent to call it correctly. No additional context is needed.
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?
Both parameters are described in the schema with 'First number' and 'Second number', achieving 100% coverage. The tool description does not add constraints or additional meaning beyond the schema.
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 uses the specific verb 'Add' and identifies the resource/action as 'two numbers,' clearly distinguishing this from sibling tools that handle connections and resources.
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 no guidance on when to use this tool relative to alternatives. It only states the operation itself, leaving the agent to infer applicability.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.