delete_many

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

No annotations exist. The description provides no behavioral details beyond the fact that it deletes; it does not disclose destructive nature, permissions needed, rollback, or side effects.

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 very short (one line), which is concise, but it lacks structure and important details. It is not front-loaded with key information beyond the endpoint.

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 simplicity (one parameter, no output schema), the description should fully explain the operation and parameter. It fails to do so, leaving the agent guessing about the resource type and parameter semantics.

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 schema has one parameter 'ids' with no description, and the description adds no meaning. Since schema description coverage is 0%, the description should clarify that 'ids' are the UUIDs of shopping items to delete, but it does not.

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 'Delete Many' and the endpoint '/api/households/shopping/items', which indicates a batch delete operation. However, it does not explicitly state what is being deleted (shopping items) and can be ambiguous among many delete sibling tools.

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 usage guidelines provided. There is no indication of when to use this tool versus alternatives like 'bulk_delete_recipes' or single-item delete tools, and no prerequisites or conditions.

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