Delete List

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Delete a list' and does not mention irreversibility, cascading deletion of contained cards/tasks, permission requirements, or any side effects. The word 'delete' implies destructiveness but lacks necessary contextual detail.

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 a single sentence with no wasted words, and the primary action is front-loaded. It is efficiently concise, though the brevity contributes to the lack of behavioral and contextual detail.

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?

The output schema and input schema cover the parameter and return value basics, but the description lacks essential context for a destructive operation. With no annotations and no side-effect or usage guidance, an agent does not have enough information to call this tool safely and confidently.

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%, and the description does not mention the 'id' parameter, what it refers to, or any constraints. Since the description must compensate for the low schema coverage, this is a significant gap—especially for a tool with one required parameter.

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 clearly identifies the operation as deleting a list, using a specific verb and resource. It distinguishes itself from sibling tools like get_list, create_list, and update_list by the action. However, it is essentially a restatement of the title and adds no detail about scope or effects.

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 when-to-use guidance is provided, nor any contrast with alternatives such as updating or archiving a list. There are no prerequisites, caveats, or conditions mentioned. The intended usage is only implied by the tool name and verb.

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