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

Annotations already indicate destructiveHint=true and idempotentHint=true, but the description adds valuable context: tasks remain searchable and appear in sprint history, are never deleted, the operation has no count or undo, and idempotency is confirmed ('a second call finds nothing left to archive'). This goes beyond the annotations to fully disclose behavior, including the need for user confirmation. No contradiction with annotations.

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 dense but well-structured. It front-loads the core purpose, then explains effects, exclusions, and idempotency. Every sentence earns its place: it covers purpose, safety, alternatives, and behavioral guarantees without redundancy. It is appropriately sized for the complexity of the operation.

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 zero-parameter, destructive tool with no output schema, the description is complete. It tells the agent when to use it, what it does, what happens to the data, how it relates to siblings, and the required confirmation step. There is no missing information that would prevent an agent from correctly invoking 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?

The tool has zero parameters, and the schema coverage is 100% (no parameters to document). The description correctly avoids explaining nonexistent parameters, and the baseline for a zero-parameter tool is 4. No additional meaning is needed since there is nothing to clarify.

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 tool's purpose: to clear the Done column by archiving all tasks in it. It uses a specific verb ('archive') and resource ('Done column'), and explicitly differentiates itself from sibling tools like complete_sprint and restore_task by explaining what it does not do (e.g., restore_task restores from trash, not archive). The purpose is unambiguous and immediately actionable.

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 description provides explicit when-to-use guidance with examples ('archive everything in Done', 'clean up the board'). It also states clear exclusions: never call on your own initiative and always confirm with the user first. It references complete_sprint as an automatic alternative for finished sprint tasks, and distinguishes this tool as covering the rest. This leaves no ambiguity about when to invoke it versus alternatives.

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