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

The annotation set is thin (only destructiveHint=true), so the description carries most of the burden. It usefully discloses auth requirements, the no-memory 'every time' rule for delivery data, and the conditional pickup rule. However it never says what committing a booking actually does commercially (cost incurred, reversibility, confirmation behavior), which matters for a destructive write operation.

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?

Four tight sentences, front-loaded with what the tool does, then preconditions, then the conditional pickup rule and the pre-call instruction. Every sentence carries information, with only mild redundancy between 'requires ... every time' and the schema's own repetition.

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 an 8-parameter tool with nested objects and no output schema, the description covers the essential call-time requirements (auth, required inputs, conditional pickup, pre-call data gathering). The main remaining gap is the outcome/return behavior of a successful booking, which the description does not address.

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 100%, so the schema already documents all 8 parameters including nested objects and required fields, establishing a baseline of 3. The description reinforces that quote_id and full delivery are required and explains quote_id provenance, but adds little semantic detail beyond what the schema fields already state.

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?

States a specific verb ('book') and resource ('quoted shipment') and explicitly ties it to output from quote tools (Warp or market carrier), which separates it from siblings like ftl_quote, ltl_quote, and batch_quote. An agent immediately understands this is the terminal booking step after quoting.

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?

Gives clear preconditions: quote_id must come from a quote tool, delivery details are mandatory 'every time', and pickup may be omitted only when a default shipper is saved. It also instructs collecting missing details before calling. It does not differentiate when to use book vs batch_book or multistop_book, so it stops short of a 5.

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