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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the rest of the burden. It discloses that the price is all-in (GST and Singapore delivery included, SGD) and that same-day to 5-day rush is available, which is genuinely useful context beyond the annotations. It does not discuss rate limits or pagination, but for a read-only quote endpoint that is a minor omission.

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?

Front-loaded with the core value (instant all-in price and ready-by date) before category detail, and every clause adds information. It is denser than needed in the first sentence, but no sentence is filler.

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, the description nonetheless tells the agent what comes back (all-in price in SGD plus a ready-by date). Combined with the clear scope boundary against request_quote, nothing an agent needs to select or invoke this tool 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?

With 67% schema coverage, the description adds real meaning: it clarifies that needed_by drives rush-option selection ('Pass the deadline to see options that make it') and lists the category values in prose, reinforcing the enum. Quantity semantics are left to the schema's own note, so it goes slightly beyond baseline but not fully.

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 (instant all-in price and ready-by date for event print/merch) and enumerates the exact product categories covered. It explicitly names request_quote as the handler for everything outside that scope, so an agent can distinguish it from siblings 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?

Gives the trigger ('Use when someone wants these printed or priced'), the key action ('Pass the deadline to see options that make it'), and an explicit exclusion routing other custom print/merch to request_quote. When-to-use and when-not-to-use are both covered.

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