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

Annotations already declare destructiveHint=true, but the description adds substantial context beyond them: the deletion cascades to all cards including archived ones, it is irreversible, and omitting confirm produces a preview with the number of cards that would be lost. That is exactly the behavioral detail an agent needs before invoking a destructive tool.

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?

Three short sentences are front-loaded with the core action, then irreversibility, then the confirmation requirement. Every sentence adds distinct information and none is padding.

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 cascade tool with no output schema and full destructive annotations, the description covers consequences, irreversibility, and preview behavior well. Minor gaps remain: listId semantics are not documented, and no permissions or side effects beyond card deletion are mentioned.

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 moderate at 50%. The confirm parameter is already fully described in the schema, and the description mostly restates that behavior while adding the preview detail ('number of cards that would be lost'). The required listId parameter remains unexplained in both the schema and the description, though its meaning is largely evident from the name.

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 (permanently deletes a list) and clarifies the cascade scope (every card, archived included). The word 'permanently' distinguishes it from archive siblings such as archive_board and archive_task, so an agent can tell it apart without opening sibling schemas.

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?

It explains the confirmation precondition ('Needs confirm: true') and the preview fallback, which is useful invocation guidance. However, it does not say when to choose delete_list over alternatives such as archive_task, update_list, or restore_task, leaving routing to inference.

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