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

It goes beyond the annotations by specifying the key behavioral traits that a quote does not commit stock or consume credit. This clearly defines the state (draft) and the lack of downstream side effects like inventory locks.

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 definition is extremely concise and highly effective. Every sentence is front-loaded and contributes to clarifying the tool's function, behavior, or parameter logic without any redundant language.

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?

The description is complete for this operational task, covering the creation state, the non-binding nature of the draft, and the specific financial conventions required for the tool to function correctly.

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?

While schema coverage is 100%, the description adds crucial semantic meaning to the 'unit_price' field by explaining the default behavior (list price) and the unit conversion (integer in cents).

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 action (Draft a quote) and the target (a customer). It establishes the function's role in the sales cycle (creating a non-committing proposal).

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?

It provides explicit usage rules for financial parameters: omitting unit_price takes the list price, and using unit_price explicitly indicates a discount in the log, guiding the agent on argument construction.

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