delete_board

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

With no annotations, the description must carry the behavioral load. It does disclose the two most important traits of a mutation: the deletion is permanent (irreversible) and gated behind confirm=true. It says nothing about permissions required, cascade effects on contained items, or failure modes.

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?

Two short sentences, zero waste, with the destructive nature front-loaded and the confirmation requirement immediately following.

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?

An output schema exists so return values need no explanation, and the required confirm gate is covered. However, for a permanent board deletion the description omits whether child items are removed, who may perform it, and whether it can be undone — material gaps for an agent deciding to call it.

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%, so the description must compensate. It adds real meaning for `confirm` (must be true, despite defaulting to false in the schema), but leaves `board_id` entirely unelaborated. Partial compensation for two parameters.

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?

Names a specific verb and resource ('Delete a board') and adds the scope qualifier 'permanently'. It reads distinctly from sibling operations like delete_item or delete_doc via the resource name, though it does not explicitly distinguish itself from those siblings in prose.

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?

Implies when to use it (to remove a board) and gives one hard prerequisite ('Requires confirm=true'), but offers no when-not-to-use guidance, no mention of alternatives like archiving, and no preconditions about board contents.

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