get_all_households

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

With no annotations, the description carries the full behavioral burden. It implies a read via the GET endpoint, but says nothing about pagination behavior, default ordering, authentication requirements, or what the response contains — notable gaps for a tool with seven pagination/ordering parameters.

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 useful content is front-loaded into two short fragments, but the bulk of the description is a bloated comma-separated keyword list that restates the name many times and adds no invocation value. Large portions do not earn their 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 paginated list tool with seven undocumented parameters, no output schema, and no annotations, the description is far too thin. It never explains paging, ordering, or filtering, leaving the agent unable to use the parameters 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?

Schema description coverage is 0% across seven parameters (page, orderBy, perPage, queryFilter, orderDirection, paginationSeed, orderByNullPosition). The description mentions none of them, so an agent gets no meaning for pagination, filtering, or ordering semantics from either the schema or 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?

States a clear verb+resource ('List households') and gives the underlying endpoint (GET /api/groups/households), so the agent knows exactly what operation this is. However, it offers no differentiation from nearby siblings like get_household, get_one_household, or explore_households_get_all, which leaves ambiguity about which household-list variant to pick.

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, only a keyword dump of synonyms for 'list households'. The agent gets no signal about choosing this over the other household-listing siblings.

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