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

With no annotations available, the description fully carries the behavioral transparency burden. It discloses that this is an 'ADVANCED/manual commit', explains it computes totals and returns a shareable URL, warns against blindly passing product_ids, and clarifies that not every retailer needs a pick.

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 description is concise and well-organized into three short paragraphs, each serving a distinct purpose: usage distinction, parameter guidance, and safety warning. Every sentence adds value without redundancy.

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?

Despite lacking an output schema, the description mentions the return value ('shareable basket URL'), provides prerequisites, explains parameter filling, and warns against misuse. It fully addresses the complexity of a manual commit tool and its relationship to siblings.

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 schema already describes the structure, but the description adds meaningful semantics: 'provide the query string and one product_id per retailer (the best match you found in batch_search results)' and 'omit a retailer if no good match was found.' This goes beyond the schema's structural descriptions.

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 clearly states the tool's purpose: to commit a basket from pre-chosen product_ids, compute totals, and return a shareable URL. It explicitly distinguishes itself from build_basket, noting that save_basket is for manual commits, not building baskets from lists.

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?

The description provides explicit when-to-use and when-not-to-use guidance: 'Do NOT use this to build a basket from a shopping list' and directs users to build_basket for lists of 2+ items. It also states the exact scenario for using save_basket: after choosing product_ids manually, e.g., after overriding a build_basket pick.

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