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

Annotations already flag destructiveHint=true, so the mutation risk is communicated structurally. The description adds the state transition (reopen/unarchive) and the POST endpoint, which confirms a write. It does not disclose side effects such as whether completion timestamps, archive status, or reporting history are affected.

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, front-loaded with the operation and its purpose. The REST endpoint line is conventional filler for this tool family rather than information an agent needs to choose the tool, but it is brief and does no harm.

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?

A one-parameter, no-output-schema tool with annotations covering the safety profile needs little prose; the description covers what the operation does and how it is invoked. The only real gap is the absence of routing guidance versus sibling task-mutation tools.

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 100% and the single 'id' parameter is documented in the schema itself ('The task id to mark incomplete'). The description only echoes the id via the URL template and adds no format or constraint detail, so baseline 3 applies.

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?

States a specific verb ('Reopen') and resource ('a completed task') with a clarifying synonym ('unarchive') and the backing REST endpoint. It is effectively the inverse of reclaim_mark_task_complete, but that sibling is never named, so differentiation is inferential rather than explicit.

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 phrase 'Reopen a completed task' implies the precondition (the task must be completed/archived), which is reasonable implied usage. However, no alternative tools are named and no when-not guidance is given (e.g., what to do for a task that was never completed, or how this differs from reclaim_update_task or reclaim_delete_task).

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