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

Annotations already mark the tool read-only and idempotent, and the description adds meaningful behavioral detail: it excludes shipping and tax ('subtotal before shipping and tax'), reports orderability and the next price break, and states that the deep_link preserves the same configured total. There are no side effects or contradictions.

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 definition is a single dense sentence that is front-loaded with the core action and then lists the returned fields and optional inputs. It contains no filler, though the long list makes it slightly heavy; still, the structure is efficient and readable.

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?

Since there is no output schema, the description compensates by enumerating the key result fields and the key exclusion of shipping and tax. The remaining gaps, such as the exact-one product identifier requirement and sizes replacing quantity, are already covered by the input schema, so the overall documentation is sufficiently complete for 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 86%, and most parameters already carry useful descriptions, such as color being 'from get_product_options' and product being identified by exactly one of slug, id, or sku. The description repeats that these inputs are optional but adds little semantic detail beyond what the schema already provides, so the 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 names the exact action, 'Price an order of a given quantity,' and enumerates the returned price components: per-unit price, setup, run charges, rush and tariff, subtotal, orderability, next price break, and deep_link. This clearly distinguishes it from sibling catalog/option/delivery tools because it is specifically about pricing a configured order.

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 when to use the tool—once a product and quantity are known—and lets the caller optionally specify color, decoration method, imprint colors, per-size quantities, and rush. However, it never explicitly says to prefer this over estimate_delivery or to first call get_product_options/get_imprint_options for valid option values, so the usage guidance is implicit rather than explicit.

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