households_shopping_lists_get_all

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

No annotations are provided, so the description carries the full burden. The [GET ...] path and the buried keyword 'read-only' hint that this is a safe read, but there is no mention of pagination defaults, ordering behavior, scope (current household vs all), or what a returned list contains. For a 7-parameter collection endpoint this is thin.

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 purpose and endpoint are front-loaded, which is good, but the bulk of the text is a long keyword-stuffing list with redundant near-synonyms (list/list lists/get list/search list/browse list/fetch list/read list). Information density is low relative to length.

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 no output schema, no annotations, and seven completely undocumented parameters, the description leaves an agent unable to call it correctly beyond the bare endpoint. An agent would not know how to filter, sort, or page the results.

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?

Seven parameters (page, perPage, orderBy, orderDirection, queryFilter, paginationSeed, orderByNullPosition) are present with 0% schema description coverage, and the description says nothing about any of them — not even that it paginates or that queryFilter searches. The description fails to compensate for the schema gap entirely.

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 resource (Households: Shopping Lists) and the action (Get All / list), and the endpoint path confirms it retrieves the collection. However, 'List lists' is close to a tautology and the text never distinguishes this from households_shopping_lists_get_one or households_shopping_list_items_get_all, so the purpose is clear but not differentiated.

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 sibling get_one, items_get_all, or the many other list endpoints. The tool name convention implies bulk retrieval, but the description offers no explicit conditions, prerequisites, or alternatives.

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