get_one_household

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

Without annotations, the description carries the full burden of disclosing behavior. It provides only the endpoint and HTTP method, with no details about side effects, required permissions, or return format. For a read operation, it is presumably safe, but this is not explicitly stated.

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 very short, consisting of just the title and endpoint. While concise, it sacrifices substance. It is front-loaded with the tool's purpose but lacks sufficient detail to be truly helpful.

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 the many sibling household tools, the description does not clarify how this tool differs from 'get_household' or others. Without output schema or behavioral details, the description is incomplete for an agent to use correctly.

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?

The input schema has 0% description coverage, meaning the schema itself provides no explanation for 'household_slug'. The description adds no parameter information—no format, source, or example is given. This is a critical gap.

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 tool retrieves a single household using the HTTP GET method and the endpoint path. The phrase 'Get One Household' is specific, distinguishing it from list tools like 'get_all_households'. However, it does not explicitly differentiate from similar siblings like 'get_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?

No usage guidelines are provided. There is no indication of when to use this tool versus alternatives such as 'get_all_households' or 'get_household'. The description lacks any contextual guidance for selection.

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