List Households Preferences

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

With no annotations, the description carries the behavioral disclosure burden, but 'Get' only implies a read operation. It does not state whether preferences are scoped to the current household, whether any side effects occur, 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 description is short, but that is under-specification rather than efficient conciseness. A single restatement of the tool name does not earn its place as a useful definition.

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?

The tool has no annotations and only a tautological description, so the agent lacks context about household scoping, response shape, or relationship to sibling preference tools. The optional accept-language parameter is completely unexplained.

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 mention the accept-language parameter or its effect on returned preferences. The schema only shows a nullable string, so an agent cannot infer language semantics or accepted formats.

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 Household Preferences' simply restates the tool name/title 'List Households Preferences' without adding any detail about what these preferences are or for whom. It does not distinguish itself from sibling list_groups_preferences or the update_households_preferences counterpart.

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 guidance is given about when to choose this tool over list_groups_preferences or other preference-related siblings. The description provides no context about households vs groups, auth, or related operations.

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