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

Beyond annotations, the description adds important behavior: the link is time-limited, the user reviews and ticks off items on that page, the tool buys nothing, and a linked Chop It account is required. It does not contradict the annotations; readOnlyHint=false fits creating a handoff link rather than a read-only lookup.

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 three focused sentences and front-loads the core action before clarifying scope and constraints. There is little waste, though the phrasing could be slightly tighter around the menu-draft alternative.

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?

Given annotations and a present output schema, the description covers the essential operator context: what link is created, what the user does with it, that no purchase occurs, and that an account is required. A minor gap is that it does not explicitly say when to prefer a shopping list versus a menu draft.

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 100%, so the schema already explains menuDraftId, shoppingListId, and expectedRevision. The description adds only light context about using a shopping list or a menu draft's derived list at its current revision, which is useful but does not materially go beyond the 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 uses a specific verb and resource: it 'Creates a time-limited Chop It review link' for groceries still to buy on a shopping list or menu draft. This is far more precise than a generic 'open shop' summary, though it does not explicitly contrast itself with siblings such as shop_week.

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 implies when to use the tool by describing the review-link flow and noting that purchases happen on a supermarket site, but it gives no explicit when-not-to-use guidance or direct comparison to related siblings like shop_week. The account requirement is a helpful prerequisite, not an alternative-selection rule.

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