update_households_shopping_items

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

No annotations are provided, so the description must fully disclose behavioral traits. However, 'Update Many' reveals nothing about whether the operation is atomic, what gets destroyed or overwritten, authentication needs, rate limits, or the response format. This is a severe gap for a mutation tool.

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?

While extremely short (two words), this is under-specification rather than effective conciseness. The description lacks structure and essential information; it should include a brief explanation of the tool's purpose and parameters.

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 high complexity of the input schema (many $defs, nested objects) and the presence of an output schema (not detailed), the description is woefully incomplete. It fails to help an agent understand what the tool does, how to invoke it correctly, or what to expect as output.

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 input schema has 0% description coverage, and the description adds no meaning to parameters. The 'body' parameter is a complex array of 'ShoppingListItemUpdateBulk' objects with many nested definitions, but the description offers no hints about what fields to set or how the bulk operation works.

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 'Update Many' is a tautology that merely restates the suffix of the tool name 'update_households_shopping_items'. It does not specify the resource (shopping items) or the action's scope (bulk update within a household), nor does it differentiate from siblings like 'update_households_shopping_items_by_item' which updates 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?

The description provides no guidance on when to use this tool versus alternatives. The sibling list includes multiple update tools (e.g., 'update_households_shopping_items_by_item'), but no context is given about when bulk update is appropriate or what prerequisites exist.

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