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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's only added value is the word "endgültig", confirming this is a hard, irreversible delete rather than an archive. It says nothing about cascade effects (widgets/content on the board), required permissions, or whether undo_change can recover it — meaningful gaps for a destructive tool, but the safety profile itself is already covered structurally.

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 filler. It is efficient, though its brevity is as much under-specification as conciseness.

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, no-output-schema tool with an undocumented required parameter, the description omits the essential context an agent needs: cascade behavior, recoverability via undo_change, and the clear_board alternative. Only the permanence fact is conveyed.

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 board_id parameter, and the description does not compensate at all — it never mentions the identifier, its type, where to obtain it, or what happens with an invalid id. The schema alone leaves the parameter undocumented.

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 verb+resource is clear (delete a board) and "endgültig" signals it is a permanent removal rather than a content reset. However, it largely restates the tool name and title, and gives no hint of how it differs from the closely related clear_board sibling.

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 on when to use this versus clear_board (clear contents) or undo_change (recover). The agent must infer the distinction from tool names alone, which is risky for an irreversible operation.

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