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

The description adds 'Secret key only' and 'Scope: quote,' but with no output schema and weak annotations, it fails to disclose key behavioral traits like whether the quote is persisted, what the response contains, or how firm-quote pricing is computed. The description carries most of the transparency burden and does not carry it far enough.

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 very compact and front-loads the core purpose: 'items or total_cuft in, firm quote out.' The extra fragments 'Secret key only' and 'Scope: quote' add useful constraints without padding. It is slightly telegraphic, but there is no waste.

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 8 parameters, nested objects, no required fields, and no output schema, this description is too thin to fully orient an agent. It only names two inputs and an auth constraint, leaving out behavior when both or neither of items/total_cuft are provided, response shape, and how this relates to the rate_card_id, distance, and weight parameters. The schema helps, but the description still leaves significant gaps.

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 high at 88%, so the schema already documents most parameters. The description's 'items or total_cuft in' highlights the two primary input alternatives, but this is already reflected in the schema descriptions ('Either this…' / '…or this'). It adds no substantial new parameter meaning.

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 states a clear function: 'Direct pricing for agents: items or total_cuft in, firm quote out.' It specifies both the inputs and the output, and the word 'firm' distinguishes it from sibling tools like ballpark_estimate. This is specific and actionable, not a tautology.

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 use for firm, direct pricing quotes and mentions 'Secret key only' as an access constraint, but it does not explicitly state when to use this tool versus alternatives such as ballpark_estimate or get_date_prices. The 'firm quote' wording provides context but no explicit when-not or alternative routing.

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