Delete board

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

The description adds no behavioral context beyond what annotations already provide. Annotations correctly indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description merely restates 'delete' without adding details like permanence, cascading effects, or permission requirements.

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?

The description is a single, front-loaded sentence with no wasted words. It conveys the essential action, resource, and identifier at the start.

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?

Given the tool's simplicity (one parameter, no output schema) and strong annotation coverage (destructiveHint, idempotentHint), the description is almost complete. It lacks explicit mention of alternates like archive_board, but the core functionality is fully specified.

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% with board_id described as 'Board UUID' and format uuid. The description's 'by UUID' reinforces but does not add new semantics. Per the baseline rule, a score of 3 is appropriate when the schema fully documents 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?

The description clearly states the action ('Delete') and the resource ('board'), and specifies the identifier type ('by UUID'). This distinguishes it from sibling tools like archive_board, unarchive_board, get_board, and delete_board_stage.

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?

The usage is implied: it deletes a board. However, it does not explicitly mention when to use this over alternatives like archive_board, nor does it state any prerequisites or consequences. The context is minimal but sufficient for a straightforward delete operation.

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