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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile carries no burden. The description adds the content shape (lists, items with list and category, low-stock materials), which is useful, but says nothing about ordering, completeness, or size of results.

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 trigger is front-loaded and the whole definition is two short clauses with no filler. The parenthetical '(with list and category)' is dense but earns its place by describing returned fields.

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 read-only list tool with full annotation coverage, one fully-documented optional parameter, and no output schema, this covers what an agent needs: the trigger, the contents, and the optional filter. Only the unresolved overlap with 'shopping_list' keeps it from being fully 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 100% for the single 'list' parameter, so the baseline is 3. The description reinforces the optional single-list semantics ('Optionally one list only') but adds no format, id-vs-name, or fallback detail beyond what the schema already states.

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 states a concrete verb and resource: it returns the Shopping cart's lists, their items (annotated with list and category), and materials running low. That is far more specific than the bare name. However, it never distinguishes itself from the near-identically named sibling 'shopping_list', leaving an agent to guess which of the two to call.

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 names an explicit trigger condition — 'when the user asks what they need to buy' — which is a genuine usage rule. The optional single-list scoping is also flagged. What's missing is any when-not or alternative routing, particularly against the confusingly similar 'shopping_list' sibling.

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