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

Goes well beyond the annotations: clarifies that nothing is ordered or charged, that checkout re-prices, that a failed pricing attempt adds nothing and returns what is missing or nearest combinations, and that a signed-in account is required (unauthenticated calls prompt sign-in). It also discloses the AU-only print/delivery scope and AUD/GST pricing, which no structured field carries.

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?

Four sentences, front-loaded with the core action before the failure, billing, and auth context. Dense and largely waste-free, though the AU-shipping/currency sentence is scope trivia that could be trimmed without hurting invocation correctness.

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 an output schema and rich annotations already present, the description fills the remaining gaps an agent needs: auth requirement, side-effect boundary (cart only, no charge), failure semantics, and regional/currency constraints. Nothing needed to call it correctly is missing.

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 50% and the nested configuration is extensively self-documented in the schema. The description adds the useful pointer that option ids follow price_job's format, but gives no field-level guidance of its own, so it hovers at the baseline for a partially documented 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?

States a specific verb and resource: prices a job with the pricing engine and puts it in the cart. It distinguishes itself from the sibling price_job by saying the configuration is 'as price_job takes them' and notes it mirrors the product page's Add to cart action, so an agent can tell exactly what this does versus the pure-pricing 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?

Explicitly states the failure path ('if the job cannot be priced, nothing is added') and what is not covered ('checkout on printdash.io re-prices, takes artwork and payment'), which effectively routes artwork/payment work to other tools. It does not name update_cart_line, remove_cart_line or clear_cart as the follow-up alternatives, so the routing picture is slightly incomplete.

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