subtract

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

With no annotations, the description carries full behavioral burden. It only says 'Subtract two numbers' and does not specify the order of operands (a - b vs b - a), nor whether it is a pure function with no side effects. For a subtraction tool, operand order is essential behavioral information.

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 short and front-loaded with the operation. It contains no filler words. However, it is slightly under-specified for a subtraction operation where operand order matters, so it is efficient but not fully complete.

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?

While an output schema exists and the tool is simple, the description omits critical context for correct invocation: the order of subtraction. Since there are no annotations and no other documentation, an agent cannot safely infer whether the result is a - b or b - a.

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%, so the description must compensate for the schema's lack of parameter documentation. The description adds no meaning to parameters a and b—it does not state which is the minuend and which is the subtrahend.

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 states a clear operation ('Subtract') and resource ('two numbers'), and the tool name itself distinguishes it from siblings like add, multiply, and divide. However, it does not explicitly differentiate itself from siblings or clarify the order of subtraction, which matters for this 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 guidance is provided about when to use this tool versus alternatives. There is no mention of context, exclusions, or situations where subtract is preferred over other arithmetic siblings.

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