get_one_household

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

No annotations are provided, so the description carries the full burden. It discloses only that this is a GET (hence read-only, echoed by the 'read-only' keyword) and that it is scoped to a slug; it says nothing about authentication, permission requirements, 404 behavior for unknown slugs, or what the response contains.

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 body is dominated by a keyword list ('get one household, get household, fetch household, read household, retrieve household, view household, show household...') that repeats the same intent many times without adding information. The useful content (one verb, one path) is buried under that padding.

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 simple single-resource read tool with no output schema, no annotations, and an undocumented parameter, the description should at least cover the slug's origin and how this differs from get_household/get_all_households. It covers neither, leaving the agent to guess.

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 coverage is 0% for the single parameter, and the description adds nothing beyond the path template {household_slug} — no format, case-sensitivity, or where the slug comes from. Since there is a real parameter to explain, the zero-coverage gap is not compensated.

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 states a verb+resource ('Get household') and the concrete endpoint GET /api/groups/households/{household_slug}, so the agent knows it fetches a single household by slug. However, it does nothing to distinguish this from close siblings such as get_household, get_logged_in_user_household, get_all_households, or get_household_members, which is exactly where differentiation matters most.

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 guidance, no prerequisites, and no mention of any alternative. The only hint is the endpoint path, from which an agent must infer that this is the single-resource variant. The rest of the text is keyword enumeration, not guidance.

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