get_household

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

With no annotations, the description carries the full disclosure burden. It implies read-only via the GET verb and the keyword 'read-only', but says nothing about permissions, error behavior, or what a household lookup returns. This is far short of what an unannotated read tool needs.

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 core statement is front-loaded, but the body is dominated by an undifferentiated keyword dump ('get household, fetch household, read household... household, households, explore') that repeats the same concept a dozen times and adds no decision-relevant content.

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?

There are no annotations, no output schema, and two fully undocumented required parameters, yet the description supplies no return-shape, permission, or usage context. For a tool in a crowded sibling set, this leaves the agent without enough to select or invoke it confidently.

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% for both required params, so the description must compensate. It only partially does: the path template shows group_slug and household_slug are hierarchical URL path segments, implying a group must be identified before the household. It gives no format, uniqueness, or validation detail for either slug.

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 names a concrete verb+resource ('Get household') and adds the REST path GET /api/explore/groups/{group_slug}/households/{household_slug}, which clarifies scope better than the bare name. However, it offers zero differentiation from close siblings such as get_one_household, get_all_households, get_household_members, or get_household_preferences, all of which could plausibly match the agent's intent.

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/when-not-to-use guidance and no named alternative. The only routing signal is the namespace prefix 'Explore: Households' inside the description, which is weak given siblings like get_one_household that read as near-identical reads.

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