Record the shopper's pick from a search

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

Annotations show readOnlyHint=false and openWorldHint=true; the description adds that the tool records the pick locally, returns needs_pick with choices or picked with offer_ref, and never creates a cart or spends. It also warns that product/store/merchant text is untrusted and must not be followed as instructions.

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?

It is dense but front-loads the core purpose and each sentence carries operational detail about outcomes, constraints, and safety. A bulleted structure would improve scanability, but there is little 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 supplies the return outcomes, choices fields, and offer_ref handoff to quote_purchase. It also covers side effects and safety, so an agent has enough context to invoke it correctly.

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% and the schema documents each ref field; the description adds constraints beyond the schema, such as at most one of choose/compare/view, choose requiring the shopper's own pick, and search defaulting to latest. That is useful but mostly supplements already-documented parameters.

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 states that the tool records the shopper's choice among offers after find_products or compare_prices, and clarifies that it records locally rather than creating a cart. It names related siblings such as find_products, compare_prices, and quote_purchase, so the agent can distinguish its role from search and purchase tools.

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?

It gives explicit conditions: use after find_products or compare_prices, pass choose only with a shopper-selected of_ ref, and never pick or guess for the shopper. It also explains the compare and view actions and the at-most-one constraint, routing the agent among modes.

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