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

Annotations already signal that this is a mutating but non-destructive operation. The description adds useful context about accepting plain-language input and gives examples, but it does not disclose behavior such as duplicate handling, quantity parsing, or what the response will be. This is adequate but not rich.

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?

Three sentences, each earning its place: the action, the input format with examples, and the trigger conditions. It is front-loaded and contains no filler or redundant schema repetition.

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?

This is a low-complexity tool with a well-described schema covering both parameters and a default for location. The description provides the action, input style, and usage triggers. It does not explain what happens after items are added, but that is not essential given the simple nature of the tool and no output schema.

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 baseline is 3. The description adds value by reinforcing the 'plain language' expectation with concrete examples like '2 lemons' and 'half a bag of spinach', which help an agent understand the intended format for the items parameter.

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 opens with 'Add items to the kitchen', a specific verb and resource that directly matches the tool's function. It clearly distinguishes this tool from siblings like list_pantry, cook_tonight, and save_recipe, which all have obviously different purposes.

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 trigger conditions: 'Use this when they mention shopping, unpacking groceries, or having bought something.' It does not mention when not to use it or name alternative tools explicitly, so it stops short of a 5.

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