clear_shopping_list

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

With no annotations, the description carries the disclosure burden and does the most important part: it flags a destructive bulk operation and documents the built-in dry-run safety gate via confirm. It omits whether the cleared items are recoverable and whether the list container survives, which are the remaining behavioral unknowns.

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?

A single tight sentence that front-loads the default preview behavior and then the confirm escape hatch. No filler, no repetition of the tool name.

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 described, and the two parameters' core semantics are covered. The remaining gap is relationship to the adjacent delete_shopping_list and remove_shopping_list_items tools, which a destructive tool should ideally disambiguate.

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 parameter's dual preview/execute semantics and default-off behavior, but says nothing about list_id beyond its name, leaving scope (which list, ID format) undocumented in both places.

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+resource: removes all shopping items from a list, and clarifies the operation is previewed by default. It contrasts implicitly with remove_shopping_list_items by emphasizing 'all', but never names that sibling to make the boundary explicit.

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 clear operational context: calling without confirm produces a preview, and passing confirm=True performs the clear. No exclusions or sibling routing are stated (e.g., use remove_shopping_list_items for selective removal or delete_shopping_list to remove the list itself), so the agent must infer those boundaries.

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