mealie_delete_shopping_item

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the destructive nature ('Delete') and adds the confirmation requirement, but it does not mention permanence, error handling, or side effects, which are important for a delete operation.

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 a single concise sentence that communicates the core purpose and key condition without any redundant information.

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?

The tool is simple, has an output schema, and the description covers the basic purpose. However, the relationship between 'explicit confirmation' and the confirmed_by_user parameter is ambiguous, and there is no guidance on what happens if confirmation is not provided. This leaves a gap for correct invocation.

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 0% description coverage. The description's 'after explicit confirmation' indirectly hints at the confirmed_by_user parameter, but it does not explain that the parameter must be set to true, nor does it clarify item_id beyond what the self-explanatory parameter name suggests.

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 clearly states the verb 'Delete' and the resource 'one shopping list item', and adds the condition 'after explicit confirmation'. This distinguishes it from sibling tools like mealie_add_shopping_item or mealie_update_shopping_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 phrase 'after explicit confirmation' provides a clear usage prerequisite: only call the tool when the user has confirmed the deletion. However, it does not explicitly mention alternatives or cases where deletion should be avoided.

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