Get Admin Households By Item

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals nothing about read-only behavior, authorization requirements, error conditions, or the effect of the accept-language parameter. "Get One" is not a behavioral description.

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 tiny, but this is under-specification rather than conciseness. There is no useful content front-loaded; the two words "Get One" waste the opportunity to convey any operational meaning.

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 tool with two parameters, no annotations, and a generic name, this description is entirely inadequate. It fails to explain what is returned, what item_id references, why accept-language matters, or how this relates to the admin households resource.

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 compensate by explaining item_id or accept-language. The schema only provides types and UUID format; the description adds no meaning about what the item ID identifies or how the language parameter affects the response.

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 is literally "Get One" — it does not state what resource is fetched, what item_id refers to, or anything about admin households. It is essentially a tautology of the verb 'get' and provides no distinguishing information against the many sibling get_*_by_item tools.

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 about when to use this tool versus alternatives such as list_admin_households or update_admin_households_by_item. The name implies retrieving a single admin household by ID, but the description gives no context, prerequisites, or exclusions.

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