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. While 'permanently' signals irreversibility, it doesn't disclose what happens to contained tasks, whether the operation requires specific permissions, or whether deletion cascades to children. For a destructive mutation with zero annotation coverage, this is a significant gap.

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?

One short, direct sentence with zero wasted words. The single-sentence form is appropriate for a tool with one parameter and a simple conceptual purpose. Clearly front-loaded with the action verb.

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 (1 param, no output schema, no nested objects), so structural complexity is low. However, for a destructive operation with no annotations and no behavioral disclosure about side effects (cascading deletions, permissions), the description is incomplete for an agent that needs to understand consequences before invoking a delete.

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% and the sole parameter list_id has a description ('The list ID'). The description implicitly confirms the list param is required for the deletion target. With a single string parameter and full schema documentation, the description adds adequate meaning; there's minimal parameter semantics to explain beyond what the schema provides.

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 states the verb ('delete') and resource ('list') with 'permanently' signaling irreversibility. It distinguishes from siblings like update_list, get_list, and create_list which all operate on lists. However, it doesn't explicitly state the scope (e.g., workspace-level) unlike the get_calls example which mentions filtering scope.

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 on when to use vs alternatives, no prerequisites mentioned, and no warning about cascading effects. With 100+ sibling tools operating on related resources (folders, tasks, spaces), no guidance on deletion implications or order of operations is provided. The description gives zero context about when this tool is appropriate.

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