list_households_preferences

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

No annotations exist, and the description only says 'Get', implying a read operation. It lacks details on authorization, rate limits, return structure, or pagination behavior, which are critical for safe invocation.

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?

At one sentence, it is concise but underspecified. The phrase 'Get Household Preferences' omits necessary context such as what preferences are included, leading to ambiguity.

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 presence of an output schema, the description could still benefit from clarifying the scope (e.g., household-wide preferences, user-specific). The current description is too vague for a tool among many similar siblings.

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 only parameter 'accept-language' has 0% schema description coverage, and the description does not mention it or provide any meaning. The agent receives no guidance on how to use this parameter.

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?

Description states 'Get Household Preferences', which indicates retrieving preferences. However, it does not distinguish from sibling tools like 'list_households_self' or 'update_households_preferences', nor clarify if 'list' implies a collection vs. 'get' implying a single item.

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 provided. The description does not specify when to use this tool over alternatives, such as 'list_groups_preferences' or 'update_households_preferences', leaving the agent without context for selection.

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