update_household

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

Annotations only declare idempotentHint, so the description carries most of the behavioral burden. It helpfully discloses the return summary (country, people count, store count, servings) and the idempotent nature is reinforced, but it never clarifies whether omitted fields are cleared or preserved (set vs. partial-update semantics) for a mutation tool with zero required params.

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?

Front-loaded with the core action, then structured with USE WHEN, a constraint, a TIP, and return info. Slightly dense but every clause earns its place; no filler.

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?

No output schema exists, yet the description summarizes the returned config, and parameter meaning is fully covered by the schema. The main missing piece is partial-vs-full update semantics for a zero-required-param mutation, keeping it short of 5.

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 coverage is already 100%, so the baseline is 3, but the description adds value beyond the schema by telling the agent to use list_stores to find dealer IDs and reiterating the country market codes. This cross-references sibling tools rather than restating field names.

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 specific verb ("Set") plus the exact resource and the fields it governs (members, restrictions, stores, country, servings). An agent can immediately distinguish this from the read-only sibling get_household without opening the schema.

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?

Provides an explicit USE WHEN clause ("first-time setup or changing household config"), a prerequisite/ordering constraint ("Required before shopping lists can filter by preferred stores"), and a cross-tool tip pointing to list_stores. Routes the agent clearly.

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