aiworkhub_dashboard_storage_purge

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

Annotations declare destructiveHint=true, and the description goes well beyond them: it names the exact effects (removes the batch directory, records an audit event, invalidates storage telemetry), the confirm=True gate, and the auth/deadline requirement. Nothing about the write's blast radius is left implicit.

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 sentences, both earning their place: the destructive warning and scope are front-loaded, then the prerequisite alternatives and side effects follow. No filler or repetition of the title.

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 an irreversible mutation with an output schema already present, the description covers the safety profile, prerequisites, recovery path, and post-conditions. An agent has everything needed to call it correctly or avoid calling 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?

Schema coverage is 100% and both parameters are documented in-schema, so the baseline is met. The description still adds meaningful state semantics — that the batch must be expired, authenticated, and past its restore deadline — which the schema's one-line param docs do not convey.

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 ('permanently delete') and a precisely scoped resource ('one expired worker-worktree quarantine batch from disk'), distinguishing it from the sibling preview, restore, and quarantine tools by its irreversible nature.

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 routes the agent: inspect with aiworkhub_dashboard_storage_retention_preview first, or use aiworkhub_dashboard_storage_restore while the undo window is active. It also states the precondition that the restore deadline must have passed, making the use condition unambiguous.

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