delete_shopping_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it only says 'Delete a shopping list.' It does not disclose that deletion is permanent/irreversible, whether deleting the list cascades to its contained items, or what happens when the ID does not exist. The cascade question is a meaningful gap given the existence of add_shopping_list_item.

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 action verb is front-loaded and both sentences earn their place with no fluff. It is brief but not absurdly under-specified like a bare verb; the brevity is proportionate to a one-parameter tool, though it contributes to missing content penalized in other dimensions.

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 destructive tool with zero annotations, the description is incomplete: it omits irreversibility, cascade behavior on contained items, and scope boundaries versus remove_shopping_list_item. The presence of an output schema covers return values, which mitigates but does not offset the missing behavioral context.

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, but 'list_id: Shopping list ID to delete' merely restates the parameter name. It adds no meaning about how to obtain the ID, its format, or whether it must reference an existing list.

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 verb and resource: 'Delete a shopping list.' This clearly identifies the operation and differentiates from list-retrieval and creation siblings by name. However, it does not explicitly distinguish scope from the sibling remove_shopping_list_item, which could plausibly be confused with deleting part of a list.

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 is given about when to use this tool versus alternatives. The description offers no mention of remove_shopping_list_item for item-level removal, no cautionary context for a destructive operation, and no prerequisite such as first fetching the list via get_shopping_lists.

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