delete_many

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

No annotations are provided, so the description carries the full burden. It never states that the operation is destructive and irreversible, whether it requires authentication, or what happens to IDs that do not exist. Only the literal word 'delete' hints at the mutation, which is thin for a no-annotation 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?

The core purpose is front-loaded, but the body is padded with an undifferentiated keyword dump ('delete_many, delete many, ... mealie') that adds no decision-relevant information and pushes the useful content to a single bare sentence.

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?

With no annotations, no output schema, and an undocumented parameter at 0% coverage, the definition leaves the agent without the destructive-behavior and input-format information needed to call this mutation correctly. The keyword block substitutes volume for substance.

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 single parameter 'ids' has 0% schema description coverage, and the description never mentions it or explains that a list of UUIDs is required. 'Delete Many' hints at plural input, but the field name, format, and required count are unexplained.

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 states a verb (delete) and resource (household shopping list items) and the HTTP path confirms scope, so the agent can identify the target resource. However, 'Delete Many' and 'Delete shopping item' (singular) are inconsistent in number, and the description never distinguishes itself from the sibling delete_one other than by the auto-generated name.

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 statement of when to use bulk deletion versus households_shopping_list_items_delete_one, and no prerequisites or exclusions. Usage is only implied by the tool name and the endpoint path.

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