update_households_preferences

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

With no annotations, the description carries full burden but provides almost no behavioral information. It does not disclose authentication requirements, side effects, validation rules, or whether changes are immediate. The three-word description adds negligible transparency beyond the tool name.

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 extremely concise (3 words) but at the cost of meaningful content. It underspecifies the tool's functionality and parameter semantics, failing to 'earn its place' by providing necessary guidance. A slightly longer description would greatly improve utility.

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 tool's complexity (10 parameters, no annotations, presence of output schema), the description is grossly incomplete. It fails to explain any parameter, return value, or behavioral context. The agent cannot make informed decisions about invocation without additional knowledge.

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 adds no parameter information. There are 10 parameters (e.g., recipePublic, firstDayOfWeek) with no explanations of meaning, allowed values, or impact. Agents cannot determine what each parameter does from the description alone.

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 tool name 'update_households_preferences' and description 'Update Household Preferences' clearly indicate the verb (update) and resource (household preferences). It is distinct from sibling update tools for other household resources (e.g., update_households_permissions, update_households_cookbooks). However, the description does not elaborate on what preferences are included, relying on 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?

No guidance is provided on when to use this tool versus alternatives (e.g., list_households_preferences to read, other update tools for related resources). The description does not specify whether it updates the current household or requires authentication, leaving the agent to infer context from the name and schema.

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