aiworkhub_dashboard_storage_restore

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

With no annotations, the description carries the full burden and does so: it declares the confirm=True gate, that existing paths are not overwritten, that Git worktree registrations are reinstated, that the batch manifest and audit log are updated, and that storage telemetry is invalidated. These are non-obvious side effects an agent could not infer from the schema.

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 lead sentence front-loads the operation, and the following sentence packs the routing rule and side effects without filler. The second sentence is dense with several clauses, but each clause carries information an agent needs.

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. Given the absence of annotations and the mutation's complexity, the description covers the safety gate, collision behavior, registration handling, and bookkeeping updates – enough for an agent to call it correctly.

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 both parameters are already documented in the schema. The description restates the confirm=True requirement and implies batch_id identifies the quarantine batch, adding no format, ID-shape, or sourcing detail beyond the structured fields – baseline 3 is appropriate.

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 with scope: 'restore a quarantined worker-worktree batch back to the repository worktree root'. It also distinguishes itself from the two nearest siblings, retention_preview and purge, by name.

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 says to use it 'to roll back a quarantine batch listed by aiworkhub_dashboard_storage_retention_preview' and to use 'aiworkhub_dashboard_storage_purge to permanently delete an expired batch instead'. Both the when and the when-not are given with the alternative named.

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