Delete a specific shopping list item by its ID to remove unwanted entries from a household shopping list. Use this action when you need to clean up or correct your meal planning data.
Delete One [DELETE /api/households/shopping/lists/{item_id}]
| Name | Required | Description | Default |
|---|---|---|---|
| item_id | Yes |
Changes observed during successful MCP inspections.
v0.2.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description implies a destructive delete operation, but no annotations are provided. It lacks details on side effects (e.g., deletion of associated items, error states), which is minimal for a mutation tool with no annotations.
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?
Extremely brief but underspecified. It fails to add value beyond the name and endpoint, making it insufficient rather than efficiently concise.
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?
For a delete operation with no annotations and no output schema, the description should provide more context about authorization, effects, and potential errors. It is not complete enough for safe 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 single parameter 'item_id' has no description in the schema (0% coverage), and the description adds no meaning. The agent receives no guidance on what this ID represents or its expected format beyond 'uuid4'.
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?
Description merely repeats the name 'Delete One' and shows the endpoint. It doesn't clarify what exactly is being deleted (a shopping list vs a shopping list item), leaving ambiguity among sibling tools like 'households_shopping_list_items_delete_one'.
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 guidance on when to use this tool versus alternatives, such as deleting a shopping list item. No prerequisites or context are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.