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

Annotations already declare destructiveHint=false, openWorldHint=true and idempotentHint=false; the description goes further by naming the side-effect boundary ('Never purchases anything', 'Leaves Saved Weeks and This Week unchanged') and the auth dependency. That is real added value. It stops short of clarifying the positive write implied by readOnlyHint=false – i.e., whether the built list is persisted and where.

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 short sentences, front-loaded with the action and its return, followed by negative guarantees and the prerequisite. No filler and nothing repeated from the schema.

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 need not be explained, and the description still summarizes them usefully. Auth and side-effect scope are covered. The remaining gap is the relationship to sibling list tools and the failure mode for a non-completed 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 coverage is 0% – menuDraftId is an unannotated string – so the description must compensate. It adds meaningful qualifiers ('exact', 'completed') that constrain which ID is valid, but it does not say where to obtain that ID (e.g., via get_menu_draft) or what happens with an incomplete draft.

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 and resource – it builds the shopping list for a given menuDraftId and returns a summary plus a Chop It review URL in a single call. The precondition 'exact completed menuDraftId' sharpens the purpose. However, it never contrasts itself with the closely-related siblings create_shopping_list and get_shopping_list, so the agent must infer the difference.

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 phrase 'exact completed menuDraftId' implies usage after a menu draft is complete, and 'Requires a linked Chop It account' states a prerequisite. But there is no explicit when-not guidance and no routing to alternatives such as create_shopping_list, which an agent could reasonably confuse with this tool.

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