subtract

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

With no annotations provided, the description must carry the behavioral disclosure burden. It implies a pure function with no side effects, but it does not explicitly state the order of operands (a-b vs b-a) or behavior on errors/edge cases. For a trivial arithmetic operation, this is acceptable but not 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 with no fluff. It is front-loaded and every word earns its place, making it highly efficient.

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 simplicity of the tool and the presence of an output schema, the description is mostly complete for a basic arithmetic operation. However, it lacks any usage context and does not explicitly state the operand order, so it is not a 5.

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 has no descriptions for parameters, so the description must compensate. It only says 'two numbers', which adds little beyond the schema's integer types. It does not clarify that 'a' is the minuend and 'b' the subtrahend, leaving potential ambiguity in the order of subtraction.

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 'Subtract two numbers' clearly states the action (subtract) and the resource (two numbers), and it distinguishes itself from sibling tools (add, multiply, divide) by naming the specific operation. It is a specific verb+resource statement.

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 offers no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or scenarios appropriate for subtraction, nor does it reference sibling tools like 'add' or 'multiply'.

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