subtract

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

Description discloses core behavior (subtract b from a) but lacks details on potential edge cases like negative results or precision, and no annotations are provided to compensate.

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?

Description is brief and to the point, but includes some redundant formatting (Args/Returns) that could be streamlined.

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?

Adequately explains parameters and return value for a simple arithmetic tool; lacks edge case handling but sufficient for basic use.

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?

Clear explanation of each parameter: 'a: Number to subtract from' and 'b: Number to subtract', adding meaning beyond the type-only 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 explicitly states subtraction operation and distinguishes from siblings (add, multiply, divide) by naming the specific arithmetic action.

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 subtract vs alternatives; usage is implied by the operation but no comparative context provided.

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