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

No annotations are provided, so the description carries the full behavioral burden, and it delivers the most important trait: the artifact-gated refusal path and its error code (handoff_required). It also notes the result carries org + bound context. It omits permissions/auth requirements, idempotency on already-closed items, and reversibility.

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 core action is front-loaded in the first sentence, followed by a terse result note and a single dense gating rule. Nothing is redundant, though the second paragraph packs three distinct conditions (playbook flag, refusal code, accepted pointer formats) into one long sentence.

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 not be explained, and the description instead covers the failure mode that matters most. Given no annotations, it is still short on the safety/permission profile and on behavior when the item is already closed, leaving a modest gap.

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%, so the baseline is 3, but the description adds real value: the work_status enum lists seven values while the description narrows the intended use to 'done' or 'cancelled', and it explains that the work_status='done' path is the one subject to the artifact_required gate. The agent and work_id parameters are left entirely to the schema.

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 (mark done/cancelled) and resource (work item), with the terminal-status scope made explicit. It does not, however, distinguish itself from the sibling work_update, which can also set work_status, so an agent must infer the boundary between them.

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 second paragraph gives a concrete precondition: if the playbook sets artifact_required, a 'done' close is refused with handoff_required until an artifact or pointer comment exists. That is genuine when-to-use context, but the description never routes the agent to work_update for non-terminal status changes or states what to do for 'cancelled' closes.

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