Prepare pantry-aware grocery list

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

Annotations declare readOnlyHint=false but destructiveHint=false, and the description usefully clarifies the write is only a draft that orders nothing, plus a pantry-exclusion side effect. It still omits repeat-call behavior even though idempotentHint=false implies duplication is possible, and no auth/permission context is given.

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?

Two tight sentences with zero filler, front-loading the core action and ending on the constraint that most affects agent decisions. Every clause carries information.

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?

For a 5-parameter write tool with no output schema and zero schema documentation, the description gives an adequate mental model but leaves parameter-level semantics (retailer, quantity/unit handling, the 40-item cap) unexplained. Adequate, not complete.

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 description coverage is 0% across 5 parameters, so the description carries the burden and only partially meets it. It gestures at items ('named groceries'), pantry exclusion (keep_even_if_in_pantry), and recipe-derived entries (meal_request_ids / use_latest_recipe), but retailer is never mentioned and no format or limit guidance is added.

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 (stage a draft) and resource (grocery list) plus its inputs (saved-recipe ingredients, named groceries) and its key filtering rule (omit what the pantry holds). The closing 'Nothing is ordered' cleanly separates it from order-placing siblings like prepare_create_recipe_cart and prepare_create_ingredient_cart.

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 'stage a draft / nothing is ordered' phrasing implies this is the pre-ordering step and hints at alternatives that actually order, but no explicit when-to-use or when-not-to-use guidance is given. The agent must infer that approval/ordering routes through prepare_approve_grocery_list.

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