clear_shopping_list

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

With no annotations, the description carries the burden of disclosing behavior. It clearly explains that the default removes only checked-off rows, and warns that passing False 'wipes the list completely — that discards unbought items too,' which appropriately signals destructive consequences. It could mention irreversibility, but the disclosure is solid.

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 compact and front-loaded with the tool's purpose, followed by a focused parameter explanation. Every sentence earns its place, and there is no redundant or vague content.

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 simple one-parameter destructively scoped operation, the description covers how to invoke it and what will happen in both parameter modes. It does not describe return values or behavior on an empty list, but those are minor for this operation and not necessary 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 description coverage is 0%, so the description is the sole source of parameter meaning. It fully explains done_only: the default True behavior, the effect of leaving items, and the False behavior with its consequence. This goes well beyond the schema's title and default value.

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 states a specific action and resource: 'Clear the shopping list after a shop.' It clearly communicates what the tool does and adds the scope of the clearing behavior via the done_only parameter. It does not explicitly name sibling tools like remove_from_shopping_list or check_off_shopping_item, so differentiation is implied rather than stated.

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?

'After a shop' gives clear contextual timing for when to use the tool. It does not explicitly list alternatives or exclusions, but the distinction between removing checked-off items and wiping the whole list provides practical usage guidance within the description.

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