List Households Self

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Returns,' implying a read operation. It does not mention authentication requirements, whether multiple households are returned, or any limitations around the data for the current user.

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 a single, front-loaded sentence with no filler or redundant phrasing. It communicates the essential purpose efficiently for a simple endpoint.

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?

The endpoint is simple, has no required parameters, and an output schema exists, so the description need not explain return values. However, it lacks behavioral and usage context, and the vague 'Household Data' leaves room for misinterpretation even with the sibling list.

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?

There is one optional parameter, accept-language, with zero schema description coverage, and the description does not mention it at all. The parameter name is somewhat self-explanatory as a language header, but the description adds no value beyond the schema's bare structure.

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 clearly states the action ('Returns') and the resource ('Household Data') scoped to the Current User, which distinguishes it from household-level sibling endpoints. It is more specific than the title, though 'Household Data' remains somewhat ambiguous about whether it returns a list of households or a single household object.

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 on when to use this tool versus alternatives like list_households_members, list_households_statistics, or list_users_self. The 'Current User' scope implies a self-service use case, but no explicit when/when-not conditions or alternative names are provided.

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