delete_list

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

The final note adds genuinely useful context beyond annotations: deletion is permanent and cascades to all items in the list. That cascade behavior is not captured by destructiveHint alone. It does not address permission requirements or what happens if the list is not found, which keeps it below a 5.

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?

Front-loaded purpose, short scannable bullets, and a one-line destructive warning at the end. Every line carries information an agent needs; nothing is padded.

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 two-parameter destructive tool with no output schema, the description covers purpose, resolution path for IDs, and deletion semantics. The remaining gap is edge-case behavior — both parameters are optional and no mutual-exclusivity or missing-argument behavior is described.

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%, so baseline is 3; the description earns extra credit by telling the agent to call get_lists to resolve an ID and by framing listName as an alternative to listId. It does not specify precedence when both are supplied, nor that both are optional (meaning neither is required).

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 opens with a specific verb+resource ("Delete a list from Skylight") and the resource scope makes it distinguishable from delete_list_item. It stops short of explicitly contrasting with sibling tools like update_list or delete_list_item, but the naming leaves little ambiguity.

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 "Use this when" bullets describe cleanup scenarios but are generic restatements of intent rather than decision criteria. There is no guidance on when to prefer this over alternatives (e.g., deleting individual items via delete_list_item, or archiving via update_list), and no prerequisites stated.

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