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

Annotations already declare destructiveHint=true, so the danger is known; the description still earns credit for disclosing the cascade behavior — the list's cards are removed along with it — which is real context beyond the annotations. It omits reversibility (is there an undo via undo_change?), required permissions, and whether cards are permanently lost.

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?

A single front-loaded sentence with zero waste. It is efficient, though its brevity edges into under-specification rather than tight concision.

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 mutation with no output schema and no parameter documentation, the description should cover return/confirmation behavior and how to identify the target list. Only the cascade-deletion fact is supplied.

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% for the single parameter list_id, so the schema only gives a bare integer type. The description says nothing about what identifies a list, how to obtain a valid list_id, or what happens with an invalid id, leaving the agent to guess.

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?

States a specific verb and resource ('Löscht eine Liste') and even adds scope detail ('samt ihrer Karten'). It does not, however, distinguish itself from sibling deletion tools such as delete_board, delete_task or delete_parent_item, so an agent must infer the boundary.

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 statement of when to use this tool versus delete_board/delete_task/delete_parent_item, no prerequisite (e.g. must be the list owner), and no caveat about confirming with the user before a destructive action.

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