shopping_list_clear_toolRemove every item from a shopping list at once. Use this tool when you need to start fresh or delete an entire list permanently. Note: action cannot be undone.
Remove ALL items from a shopping list. This cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| list_id | No | Shopping list ID to clear (default 1). |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral disclosure burden. It explicitly warns that the operation cannot be undone and uses 'ALL items' to disclose the destructive scope. It does not cover permissions or partial failure, but the core irreversible behavior is well conveyed.
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?
Two short sentences front-load the core action and add a critical warning. There is no filler, repetition, or unnecessary detail.
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 single-parameter destructive tool with an output schema, the description is adequate: it tells the agent what happens and that it is irreversible. It doesn't explicitly state that the list remains after clearing, but that is inferable and not critical 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?
Schema coverage is 100%, and the list_id parameter is already documented with a default and description. The description adds no extra semantic detail for the parameter, so the baseline 3 applies.
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?
States the action (remove), the resource (shopping list), and the scope (ALL items), distinguishing it from sibling tools that operate on individual items. The irreversibility warning further clarifies intent.
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 mention of 'ALL items' clearly signals bulk clearing, which implies it is not for single-item removal. However, it does not explicitly name alternatives like shopping_list_remove_tool or provide explicit when-to-use conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.