update_household_preferences

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

With no annotations, the description carries full behavioral burden. It discloses that this is a PUT-style full replacement, but does not state permission requirements, whether omitted fields are reset to defaults, whether existing preferences are destroyed, or what the response looks like.

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 first sentence is useful and front-loaded, but the long keyword list is repetitive SEO filler that does not help an agent select or invoke the tool. The description is unnecessarily bloated for the information it conveys.

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 mutation tool with no annotations, no output schema, and 0% parameter description coverage, the definition is incomplete. It says what endpoint and that it replaces preferences, but leaves the agent without the field-level guidance needed to call it 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?

Schema description coverage is 0%, and the description does not name or explain any of the nested body fields such as recipePublic, firstDayOfWeek, or privateHousehold. It adds no parameter meaning beyond the schema itself.

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?

States a clear verb and resource: update household preferences, plus 'Replace (full update)' and the PUT endpoint. It distinguishes itself from a retrieval tool like get_household_preferences, but does not explicitly name siblings or contrast with update_group_preferences.

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?

The phrase 'Replace (full update)' implies when to use it: for a full preference replacement rather than a partial edit. However, it gives no explicit when-not conditions, prerequisites, or alternatives such as update_group_preferences or get_household_preferences.

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