households_shopping_lists_get_one

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read via 'get'/'read-only' and the GET method, but says nothing about authentication requirements, what happens if item_id does not exist or belongs to another household, or the response shape.

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 first two fragments are minimal, but the description is dominated by a long comma-separated keyword dump ('get list, fetch list, read list, retrieve list, view list, show list...') that adds no information. Most of the text does not earn its place.

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 simple single-parameter read with no output schema and no annotations, the endpoint reference is the one genuinely useful element. Still, it omits what the returned list contains and how to obtain a valid item_id, leaving the agent to infer everything from the route.

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?

There is a single parameter (item_id) with 0% schema description coverage — the schema only declares type string/uuid4 without explanation. The description adds no meaning about what item_id identifies or where it comes from, so it fails to compensate for the coverage gap.

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 verb+resource ('Get list') for a households shopping list and pins it with the HTTP endpoint GET /api/households/shopping/lists/{item_id}. However, 'Get One — Households: Shopping Lists. Get list.' largely restates the tool name and does not distinguish it from the sibling households_shopping_lists_get_all (which lists vs. this which fetches one).

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?

There is no guidance on when to use this versus the near-identical siblings households_shopping_lists_get_all or households_shopping_list_items_get_one, nor any note about prerequisites (e.g., needing a valid household/session). The keyword list is not usage guidance.

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