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

Goes well beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false): discloses that nothing is charged, that quantities round up to whole packs, that prices are recalculated from today's data, that the link is single-use with a 30-minute expiry, and that unaddable items come back in needs_quote. This is exactly the operational context annotations cannot carry.

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 compact sentences, each carrying distinct information (what it makes, cost behavior, link lifetime/geography, error handling), with the core purpose front-loaded. No 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?

An output schema exists, so return values needn't be spelled out, yet the description still flags the important output signal (needs_quote). For a single-parameter creation tool the agent has everything needed to call it correctly 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: prices are recalculated from today's data, rounds are applied to pack sizes, and items rejected for pre-order/price-on-request/stock land in needs_quote. It clarifies the practical effect of the items/stems inputs rather than restating them.

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+resource (create a one-time checkout link to a cart on nb8floral.com) with the exact scope: pre-filled with given products, nothing charged. This clearly separates it from siblings like create_quote_request and search_products.

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 strong contextual guidance: the cart is reviewed and paid on nb8floral.com, the link is single-use and expires in 30 minutes, and US-only shipping applies. It implies the quote path via needs_quote for unaddable items, but never explicitly names create_quote_request as the alternative when a checkout link isn't suitable.

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