aiworkhub_dashboard_storage_quarantine

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

With no annotations, the description carries the full burden and does it well: it declares this is a write, that the move is reversible with an undo deadline, that a signed batch is created, that an audit entry is written, and that cached storage telemetry is invalidated. It also notes fail-closed behavior on a stale digest via the requirement for an unchanged preview_digest.

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?

Front-loads the operation and its reversibility, then the prerequisite and alternatives — good ordering. The 'USER WRITE:' prefix and dense second sentence pack several facts together, which is efficient but slightly compressed.

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 needn't be explained; what remains — preconditions, reversibility, side effects (audit entry, cache invalidation), and the recovery path — is all present. Nothing an agent needs in order to call it safely is missing.

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% and both parameters are already documented with defaults and the fail-closed stale-digest rule. The description's repetition of 'requires confirm=True and an unchanged preview_digest' restates the schema rather than adding new semantics, 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 and resource ('move ... worktrees ... into a reversible quarantine batch') plus the scope constraint ('matching a current preview'). It is clearly distinguishable from the sibling preview/restore/purge tools and from the terminal-log and task quarantine variants.

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?

Explicitly names the prerequisite tool (storage_retention_preview to obtain preview_digest) and the alternative paths (restore to undo, purge to delete an expired batch). When-to-use and when-to-use-something-else are both spelled out.

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