add

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the operation but does not explicitly mention side effects, return behavior, or purity. For a simple integer addition, the operation itself implies a deterministic calculation, and the output schema covers the return shape.

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 three words long and completely front-loaded. Every word is meaningful and there is no filler. For a tool this simple, this is an appropriately efficient size.

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 input schema fully defines the two required integer parameters, the description defines the operation, and an output schema exists. An agent has all the information needed to select and invoke the tool correctly. Nothing essential is missing.

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%, and the description does not name 'a' or 'b' individually. However, 'two integers' clarifies that both parameters are operands of the addition, which is sufficient for a commutative two-parameter operation. No further parameter-specific detail is necessary here.

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 a specific verb and resource: 'Add two integers.' This clearly states the operation and distinguishes it from siblings like multiply, echo, and get_user_profile. There is no ambiguity about what the tool does.

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 clear context: use this tool when two integers need to be summed. It does not explicitly name alternatives or exclusions, but the operation is self-evident and distinct from the sibling tools. No prerequisites or special conditions are needed.

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