aiworkhub_dashboard_task_quarantine_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 well: it declares USER WRITE, requires confirm=True, mentions collision checks, transactional reinsertion of tasks/task_events/callback rows, batch restoration, and telemetry invalidation. It does not fully specify collision failure behavior or permission/auth requirements, so it falls short of a 5.

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 write-operation cue is front-loaded, followed by usage routing and then behavioral details. The description is dense but every clause adds relevant information, with no filler.

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?

Given full parameter schema coverage and an output schema, the description provides enough context to invoke the tool correctly: it covers prerequisites, transactional behavior, side effects, and alternatives. The main remaining gap is what happens when a task_id collision is detected.

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%, so both parameters are already well documented. The description reinforces that confirm=True is required and that batch_id identifies one quarantine batch, but adds little beyond the schema, making the baseline 3 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?

The description states a specific verb and resource: restore one archived-task retention batch into canonical task tables. It also distinguishes the operation from single-task restore and from the retention preview, so an agent can identify the tool without inspecting siblings.

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?

It explicitly says to use this tool to roll back a batch listed by aiworkhub_dashboard_task_retention_preview, and directs the agent to aiworkhub_dashboard_task_restore instead for a single live task. The alternative and selection condition are both stated.

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