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

Annotations declare a non-read-only, non-idempotent, open-world write, and the description adds substantial context beyond that: consent requirement, 200-image/500-unit/500-print limits, flat-rate shipping caveat (never multiply by quantity), coupon validation, and the meaning of price.total vs price.discount. This is exactly the behavioral detail an agent needs for a mutating order tool.

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?

Dense but front-loaded, leading with the core purpose and productId default before the mode-specific rules. It is long and somewhat run-on, but nearly every sentence carries operational rules that earn their place.

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?

For a complex nested-schema order tool with an output schema, the description covers the tricky parts: mode selection, calendar/composition assembly rules, limits, shipping pricing semantics, and consent. Return values are covered by the output schema and the price field explanation, so nothing critical 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?

With 0% schema description coverage, the description carries the burden and does so well: it explains items structure, photoId vs photoIds, quantity counting complete products, productId defaulting and per-item override, calendar fields, and couponCode. It leaves campaignId and the individual shipping fields unexplained, so not fully complete.

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 (quote) and resource (prints) with scope: private uploaded photo IDs plus a US destination, productId defaulting to photo-4x6 from list_products. It clearly frames the tool as producing a priced order. It does not explicitly distinguish itself from the pricing siblings estimate_print_price and preview_print_price, which is the main gap.

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?

Gives detailed when-to-use guidance for the item modes: single image via photoId, multi-image design via photoIds, calendar via calendar object, composition via per-image dimensions. It does not state when to prefer this over estimate_print_price or preview_print_price, so the sibling routing is left implicit.

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