Get Groups Households By Household Slug

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

With no annotations provided, the description carries the full behavioral disclosure burden, but 'Get One Household' only implies a read operation. It discloses nothing about required scoping, authentication, error behavior, or response semantics, leaving the agent without important operational context.

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 short, but this is under-specification rather than effective conciseness. 'Get One Household' is a single vague phrase with no structure, no context, and no detail to help an agent act.

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 the tool is simple and has an output schema, the description omits the slug-based selection mechanism, the resource scope, and parameter semantics. An agent cannot confidently select this tool over several similar household-related siblings based on the description alone.

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 explain either parameter. The required household_slug parameter is not described as the identifier for the target household, and the optional accept-language parameter is entirely unaddressed.

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 One Household' states a verb and an object, so it communicates a single-household retrieval, but it is vague about the resource scope. It does not mention the 'groups' context or that the lookup is by household_slug, and it fails to distinguish itself from sibling tools like list_groups_households or get_explore_groups_by_group_slug_households_by_household.

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. The description gives no context such as 'use this to fetch a specific household by its slug as opposed to listing households.' An agent would have to infer the intended use from the tool name and sibling list.

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