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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered, but the description adds substantial context on its own: what the branded price actually covers per product line, when digital or laser/embroidery changes that coverage, the presence of a wholesale no-setup quote, and that prices are AUD ex-GST with freight excluded per job. That is real disclosure beyond the structured fields, though it says nothing about failure modes such as an unknown pid or an invalid quantity.

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 core purpose is front-loaded in the first clause, which is good, but the remainder is one dense run-on with nested parentheses and backticked field names that is hard to parse on a first read. The content is largely relevant, yet a short bulleted breakdown of branded vs wholesale pricing would carry the same information with less cognitive load.

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?

With no output schema available, the description does the work of explaining the return payload: branded price plus setup, the brandingIncluded breakdown, the optional fullColourExtraAudAt100 field, and a separate wholesale quote. What it leaves out is edge-case behaviour (unknown product, zero or non-integer quantity) and how this quote relates to quote_options, which an agent may still need to resolve.

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 pid, quantity and locale are already documented in the schema and the baseline of 3 applies. The description adds some framing around quantity (the full-colour extra is expressed at 100 pcs) but does not explain how locale interacts with the stated AUD ex-GST pricing, so it does little 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?

The opening clause names a specific verb and resource ('Get a pricing quote for a product at a specific quantity') and immediately scopes the result as branded price plus setup, with a separate wholesale quote called out. That combination is distinctive enough that an agent can separate this from sibling price tools such as get_entry_pricing and quote_options without opening a schema.

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?

Usage is implied by the phrasing (use it when you have a pid and a quantity and need a price), and there is one strong behavioural rule: never estimate a full-colour extra that is not on file. However, there is no explicit routing guidance against quote_options or get_entry_pricing, which are the closest alternatives, so an agent still has to infer which price tool to call first.

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