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. 'Delete' makes the destructive nature clear, but the description does not state whether deletion is permanent, whether permissions are required, or whether dependent data like tasks or comments is removed. This is a meaningful gap for a destructive operation.

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 front-loaded sentence with no filler or redundancy. It is appropriately short for a one-parameter operation, though its brevity contributes to the lack of behavioral and usage context.

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 tool is simple and the schema covers the only parameter, so a one-line description is nearly sufficient for basic invocation. However, with no annotations and no output schema, the description does not disclose return behavior, error semantics, or side effects, leaving clear contextual gaps.

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?

The input schema fully documents the single required parameter with 100% coverage, so the baseline is 3. The description's 'by ID' only restates the purpose of list_id and adds no extra meaning such as ID format, source, or constraints.

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 ('Delete') and resource ('a list'), making the core purpose immediately clear and distinguishing it from sibling tools like delete_task or delete_folder. It does not add scope or variant context, but the delete-list intent is unambiguous.

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?

There is no guidance about when to use this tool versus alternatives such as update_list or delete_folder, and no mention of prerequisites or exclusions. The agent must infer usage entirely from the tool name and brief description.

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