List Groups Households

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get All Households' only states the result and does not mention pagination behavior, authentication requirements, scoping, filtering semantics, or any side effects. There is no useful behavioral context beyond the basic action.

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 very short, but for a tool with eight parameters and no annotations, this is under-specification rather than effective conciseness. It front-loads the basic action but omits any operational details needed to use the tool correctly.

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?

Although an output schema exists, the description is far too sparse for correct invocation. It does not explain how 'All' interacts with pagination or queryFilter, what group scope applies, or any requirements around parameters. An agent might guess a no-argument call but cannot construct a meaningful filtered or ordered request.

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%, and the description does not compensate. All eight parameters, including page, perPage, queryFilter, orderBy, orderDirection, paginationSeed, accept-language, and orderByNullPosition, are left completely unexplained. An agent cannot know their syntax, defaults, or meaning from this definition.

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 uses a clear verb ('Get') and a resource ('All Households'), so an agent can tell this is a read operation. However, it does not mention the 'groups' context implied by the tool name or differentiate it from similar siblings like list_households_self or list_explore_groups_by_group_slug_households. It is clear but lacks 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 guidance about when to use this tool versus the many sibling list tools, and no exclusions or scope clarification are provided. The description only states what it returns, not when it should be selected. An agent must infer usage entirely from the name.

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