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

With no annotations, the description carries the full burden, and it delivers: it explains what brandingIncluded covers, the colour/method caveats, when the full-colour extra is on file vs quoted on request, the wholesale option, AUD ex-GST pricing, and freight handling. The explicit 'never estimate it' instruction is especially valuable.

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 long but dense and front-loaded with the core action. The parenthetical caveats are somewhat heavy, yet every sentence adds relevant pricing behavior rather than filler.

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?

There is no output schema and no annotations, so the description must explain return semantics. It covers key output fields, currency, freight, and fallback behavior. It does not fully specify the response structure or error cases, but it is complete enough for correct invocation.

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 coverage is 100%, so the baseline is 3. The description adds useful context around quantity (e.g., the 100 pcs extra) but does not add new parameter-level syntax or format details beyond the schema.

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?

Opens with a specific verb and resource: 'Get a pricing quote for a product at a specific quantity.' It further differentiates the quote scope by distinguishing branded price plus setup from wholesale/unbranded, so an agent can tell this apart from a generic quote_options tool.

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 intended use is clear: quote pricing for a product at a quantity. It does not explicitly name sibling alternatives or exclusions, but the context is unambiguous enough that an agent knows when to call it.

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