divide

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

Annotations already mark the tool as read-only and idempotent, and the description adds critical behavioral context: the divisor must be non-zero and DivisionByZeroError is raised for b=0. This goes beyond the structured annotations.

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 uses a clear Args/Returns/Raises structure with no wasted words. Every sentence adds necessary information: the role of each parameter, the error handling, and the return value.

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?

For a two-number pure function, the description covers inputs, output, and error handling. The presence of an output schema reinforces the return value, and the description is self-contained.

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 only defines a and b as numbers with no descriptions. The description explicitly labels a as the dividend and b as the divisor, and adds the non-zero constraint and error condition, fully compensating for the 0% schema coverage.

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 opens with 'Divide the first number by the second,' which clearly states the operation and its two inputs. This distinguishes it from sibling arithmetic operations like modulus, power, and square_root.

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 division semantics and the non-zero constraint, but does not explicitly discuss when to use division versus alternatives. However, the context is intuitive enough for an agent to select this tool for quotient calculations.

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