warp_box_truck_quote

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

The description adds behavioral context beyond annotations (readOnlyHint=true) by noting 'firm price' and '15-min expiry'. This helps the agent understand the pricing behavior and time sensitivity. No contradiction with 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 is a single, dense sentence containing key constraints and behaviors. It is front-loaded and contains no unnecessary words.

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?

Given the tool's complexity (8 parameters, no output schema), the description covers high-level behavior (pricing, expiry) but lacks details about the response structure. However, the 100% schema coverage compensates, making the description adequate for an agent to understand the tool's role.

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 description does not need to add per-parameter details. The description provides overall context (26' truck, firm price) that aids understanding but does not add significant meaning beyond the schema. Baseline score of 3 is appropriate.

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 tool's function: 'Quote a 26' box truck shipment' with specific constraints (1-12 pallets, firm price, 15-min expiry). This distinguishes it from sibling tools like warp_ftl_quote, warp_ltl_quote, and warp_van_quote by specifying the truck type and capacity.

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 implies usage for box truck quotes but does not explicitly state when to use this tool versus alternatives. However, the context from sibling tool names and the clear purpose allow an agent to infer appropriate usage. No exclusions are provided.

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