list_groups_households

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

The description 'Get All Households' lacks behavioral disclosure. It does not mention pagination, filtering, sorting, or any side effects. With no annotations, the description should convey more about the tool's behavior, such as that it returns a list or that pagination parameters exist.

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?

While brief, the description is too sparse. It consists of only four words, which is under-specification rather than effective conciseness. Important details about parameters and behavior are omitted.

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?

Given 8 optional parameters, no annotations, and an output schema, the description is completely inadequate. It does not explain pagination, ordering, or filtering capabilities, leaving the AI agent without essential guidance.

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%, yet the description adds no information about the 8 parameters (page, orderBy, perPage, queryFilter, etc.). The description fails to explain what these parameters do or how they affect results.

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 'Get All Households' clearly states the action and resource. However, it does not distinguish from the sibling tool 'list_admin_households', which also lists households. The tool name suggests group context, but the description does not clarify this.

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?

No guidance is provided on when to use this tool versus alternatives like 'list_admin_households' or 'get_admin_households_by_item'. The description does not mention any prerequisites or context for usage.

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