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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds substantial domain behavior: prices are INR with shipping and GST included, online payment adds a Razorpay method fee, shipping is India-only, per-piece pricing lives in piece_prices, and coupons never drop below the enterprise making cost. This is real context an agent cannot get from the annotations.

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 lead clause is front-loaded and every sentence carries a distinct domain fact, so nothing is padding. However, it is delivered as one dense run-on sentence with stacked parentheticals, which makes it harder to scan than a short bulleted breakdown would be.

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 input parameters and no output schema, the description carries the full burden of explaining the return payload, and it does so by naming each returned section (SKUs, formats, sizes, limits, prices, coverage) plus the nested field path formats[].sizes. An agent has enough to call it and interpret the result.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly adds no parameter detail and instead spends its space on response structure and downstream parameter routing (formats[].sizes ids passed as size on create_order).

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+resource ("List what can be printed") and then enumerates exactly what the listing contains: SKUs, formats, trim sizes, page-count limits, prices, and shipping coverage. An agent can distinguish this catalog-lookup tool from create_order, get_order, and validate_pdf without opening any 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?

Ends with explicit sequencing guidance, "Call this first to quote a price," and routes related actions to named siblings (online_payment for the fee, create_order for coupons and the size id). It gives clear when-to-use context but states no explicit exclusion or precondition (e.g., whether auth is needed).

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