List Households Shopping Items

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure, and it does not. 'Get All' gives no information about read-only behavior, result bounds, pagination semantics, sorting behavior, or any authentication or household-scope requirements. Agents are left with no behavioral understanding beyond the tool name.

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 extremely short, but this is under-specification rather than effective conciseness. 'Get All' is an unstructured fragment that provides no sentence-level meaning and no operational detail. It is not an example of efficient, well-structured documentation.

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 an 8-parameter listing endpoint with no annotations, an output schema, and a very large sibling set, this description is severely incomplete. It omits the resource, pagination behavior, filtering/ordering semantics, and any relationship to related shopping-list tools. An agent has almost no basis to invoke this tool correctly.

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 schema has 8 parameters and 0% description coverage, and the description mentions none of them. There is no explanation of page, perPage, orderBy, queryFilter, orderDirection, paginationSeed, accept-language, or orderByNullPosition. An agent cannot infer how to construct a meaningful request from the description.

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 is 'Get All', a two-word fragment that essentially restates the listing behavior implied by the tool name. It does not explicitly name the resource (household shopping items) or provide any scope, and it does not help distinguish this tool from siblings such as list_households_shopping_lists.

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 about when to use this tool versus alternative listing tools like list_households_shopping_lists or get_households_shopping_items_by_item. The description gives no context about pagination, filtering, required household scope, or typical use cases. It is not misleading, but it offers zero direction.

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