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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered and 'Read-only' in the description is partly redundant. That said, 'as the person sees it' and the split between still-to-buy and recently-bought items are genuine behavioral details about what the response contains and how the view is personalized.

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 a tight two-sentence block that front-loads what is returned and closes with the read-only qualifier. Every clause earns its place with no filler.

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 single-optional-parameter read tool with full schema coverage, complete annotations, and an output schema, the description provides everything needed to select and invoke it. Return-value explanation is not required given the output schema, yet the content split is still summarized usefully.

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 100% on the single 'household' parameter, including the example name and the guidance to omit it for single-household people, so the schema carries the load. The description adds no parameter-level detail beyond that, making the baseline 3 appropriate.

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 names a specific verb (read) and resource (the household's shopping list), then enumerates its contents: items still to buy (with itemId) and items bought recently. It also distinguishes itself from the sibling check_shopping_items, which consumes the itemIds this tool returns, so an agent can tell the two apart without opening a schema.

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 clearly frames this as the read/view operation and names check_shopping_items for the follow-up action on the returned itemIds, giving strong context for the read-then-check workflow. It stops short of explicit when-not guidance or stating prerequisites, so it falls 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.