whiteboard_delete_board

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

Beyond the `destructiveHint: true` annotation, the description explicitly adds crucial behavioral traits: the operation is '不可撤回' (irreversible), and it provides the important caveat that '不会删除原始映射文件' (it will not delete the original mapping file).

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 definition is highly dense and efficient, covering scope, required inputs, behavioral constraints, and critical data preservation warnings in a minimal, impactful structure.

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?

The definition is highly complete. It not only details what the tool does but also addresses the critical 'how' (confirmation, version control) and 'what ifs' (irreversibility, file preservation).

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?

Since the schema description coverage is 0%, the description is responsible for defining semantics. It effectively clarifies the required constraints of 'confirm=true' and the purpose of providing 'expectedVersion.'

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 uses a specific verb ('删除' - delete) and clearly defines the resource ('整张白板' - entire whiteboard). It explicitly distinguishes itself from sibling tools like those related to element deletion.

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 provides explicit usage constraints, requiring 'confirm=true' and strongly suggesting the use of 'expectedVersion.' This guides the agent on necessary input conditions for a successful and safe call.

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