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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: entries are returned in list order, recently bought entries are included alongside open ones, and the `sentToBringAt` field signals whether an entry was already pushed to Bring!. It does not mention any result-size limits or pagination.

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 short sentences, each earning its place: what the list is, how to read `sentToBringAt`, and what is excluded. The scoping information is front-loaded and there is 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?

With zero parameters and no output schema, the description carries the burden of describing the return set, and it does so adequately by explaining ordering, inclusion of recently bought entries, and the meaning of one key field. Minor gaps remain around result volume and whether anything else is truncated, but nothing essential for correct invocation is missing.

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?

The tool takes no parameters, so the baseline is 4 and there is nothing the description needs to compensate for. The description instead spends its words clarifying a returned field (`sentToBringAt`), which is helpful framing rather than parameter documentation.

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 the exact resource (the signed-in user's food shopping list) and its composition (open entries in list order plus recently bought ones), which is more specific than the tool name alone. It also carves out supplements, distinguishing it from the Stackwell shopping-list siblings, though it never names those siblings explicitly.

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?

Usage is implied rather than stated: the agent learns this covers food items only and that supplements live in Stackwell, which is a useful exclusion. However, there is no explicit 'use this when / use stackwell_get_shopping_list instead when' routing, and no statement of prerequisites for calling it.

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