delete_shopping_list

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

With no annotations present, the description carries the full burden and it does disclose the most important trait: the default is a non-destructive preview and only confirm=True destroys data, and the deletion is stated as permanent. It doesn't say what happens to the list's items, whether the call errors on a missing list, or what permissions are needed.

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?

One sentence, front-loaded with the default (preview) behavior and ending with the opt-in destructive action. Nothing extraneous to trim.

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?

An output schema exists, so return values needn't be explained, and with only two parameters the description covers the one that matters. Minor gaps remain around side effects on list items and behavior for an invalid list_id.

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 description coverage is 0%, so the description must compensate; it fully explains the confirm flag's two values and the default behavior, which is the only non-obvious parameter. list_id is left implicit, relying on the name alone.

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 a specific verb and resource (delete a shopping list) plus the two-mode semantics folded into the same sentence. It does not differentiate from the nearby clear_shopping_list or remove_shopping_list_items siblings, which an agent could plausibly confuse with this.

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?

Gives a clear operational rule: the default call previews, and confirm=True performs the permanent deletion. What's missing is any guidance on when to prefer this over clear_shopping_list or remove_shopping_list_items.

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