add

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

The operation is inherently transparent (simple addition). The description adds no beyond what the name implies, but for this elementary tool, that is adequate. No contradictions with missing annotations.

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 extremely concise (three words) and front-loaded with the essential information. Every word is meaningful with no wasted content.

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?

The tool is simple with clear inputs and an output schema likely defining the result. The description covers the core functionality completely for this trivial case.

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 0%, but the description 'Add two numbers' implies both parameters are the numbers to be added, providing minimal added meaning. The parameter types (integers) are already clear from 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?

Description clearly states the action ('Add') and the resource ('two numbers'), leaving no ambiguity. The verb-resource combination is specific and sufficient for this simple arithmetic 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?

No explicit guidance on when to use this tool versus alternatives, but given its simplicity and the absence of sibling tools, the implied usage is straightforward. However, it lacks any context-specific recommendations.

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