Delete Households Shopping Items

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

No annotations are provided, so the description carries the full burden of explaining side effects. 'Delete Many' only indicates a bulk destructive action; it does not disclose permanence, household scoping, idempotency, permission requirements, or what happens to associated data.

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?

Three words is under-specification rather than effective conciseness. The description lacks structure, front-loaded details, and any complete sentence that an agent could use to understand the operation.

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?

This is a destructive bulk operation with no annotations, an opaque schema, and a description that provides almost no operational context. The presence of an output schema does not compensate for missing information about what gets deleted and how the ids parameter should be used.

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 meaning to the ids array or accept-language parameter. 'Many' only loosely implies multiple items and does not explain that ids must be UUIDs or that the parameter is optional.

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 'Delete Many' conveys a bulk delete operation and loosely differentiates this from delete_households_shopping_items_by_item, but it does not state what resource is being deleted or in what context. The agent must infer the target from the tool name, making the description too vague to stand alone.

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?

There is no guidance about when to use this tool versus delete_households_shopping_items_by_item or other household shopping item operations. 'Many' implies batch usage, but the description never says to use this when deleting multiple items, nor does it mention any alternatives or exclusions.

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