warp_ltl_quote

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

The description complements the readOnlyHint annotation by adding behavioral constraints such as not editorializing results, not recommending carriers, and presenting Warp's quote first. There is no contradiction; it adds important context beyond what annotations provide.

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 concise with four sentences, each serving a purpose. It front-loads the primary function and includes necessary behavioral instructions without superfluous text.

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 the description covers input usage and behavioral guidelines well, it lacks explicit details about the output format or structure. The phrase 'Present Warp's quote first, then list market options as context' provides some output context, but the absence of an output schema makes it slightly less complete for an agent to precisely understand the response.

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 input schema has 100% coverage, but the description adds value by explaining that providing dims+commodity yields a firm quote, while omitting them yields indicative pricing with FAK rates. This semantic guidance is not present in the schema descriptions.

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 'Quote an LTL shipment' and distinguishes between firm and indicative quotes based on providing dims and commodity. It uniquely identifies this as an LTL-specific tool, differentiating from siblings like warp_ftl_quote and warp_box_truck_quote.

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 explicit guidance: when to provide dims+commodity for firm quotes vs omit for indicative pricing, and how to present results (do not editorialize, present Warp's quote first, then market options). It also tells the agent not to recommend a carrier, ensuring proper usage.

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