add

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

With no annotations provided, the description carries the full burden of disclosure. 'Add two numbers' completely and accurately describes the tool's behavior: it is a pure function with no side effects, no destructive actions, and no hidden complexity. The simplicity of the operation makes the description fully transparent.

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 that gets straight to the point. It is appropriately sized for the tool's simplicity, with no wasted words or irrelevant 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?

Given the extreme simplicity of the tool and the presence of an output schema, the description is complete. It covers the operation, the parameters are straightforward, and sibling tools are clearly unrelated, so 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?

The schema covers 0% of parameter descriptions, so the tool description must compensate. 'Add two numbers' confirms that both a and b are the operands for the operation, adding some semantic context. However, it does not explicitly describe the return value or edge cases, relying on the output schema for those details.

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 tool's function: adding two numbers. It uses a specific verb (add) and resource (two numbers), making it easily distinguishable from sibling tools like fetch_page and search_docs, which serve entirely different purposes.

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 when to use the tool (whenever addition of two numbers is needed) but provides no explicit guidance on alternatives or conditions. Sibling tools are clearly unrelated, so the context is clear, but the description could be more explicit about its scope.

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