explore_households_get_all

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

With no annotations, the description carries the full burden. It offers only the keyword 'read-only' as a safety signal but says nothing about pagination behavior (despite page/perPage/paginationSeed params), auth requirements, or what the response contains for a list operation.

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 correctly front-loaded in the first two lines, but the bulk of the description is a bloated keyword dump repeating trivial morphological variants ('list household, list households, get household...'). That padding adds noise rather than value.

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, 0%-documented, annotation-free list tool with no output schema, the description is far too thin. It neither explains the filtering/sorting/pagination parameters nor clarifies its relationship to the many sibling household tools.

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 0% across 8 parameters, so the description must compensate and largely does not. The endpoint path hints that group_slug is required and path-based, but orderBy, orderDirection, queryFilter, paginationSeed, page, and perPage are left entirely unexplained.

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 specific verb and resource ('List households') and even gives the HTTP endpoint, so the operation is unambiguous. However, it does nothing to distinguish itself from the near-identical sibling 'get_all_households' (and 'get_one_household'), so it falls short of full sibling differentiation.

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 when-to-use or when-not-to-use guidance, and no mention of alternatives despite several overlapping household-listing siblings. The keyword block restates synonyms but provides no selection logic, and the endpoint only implies that a group_slug is required.

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