aiworkhub_manager_reconcile_dead_processing

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. 'WRITE' and 'reconcile' imply a mutation, and 'exact authenticated' hints that precise matching credentials/identifiers are required, but the description does not state what state is changed, whether it is idempotent or reversible, or what authorization is needed. For a zero-annotation mutation tool this is a significant gap.

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?

It is a single short sentence with no padding, and the write-nature is front-loaded via the MANAGER WRITE prefix. But the terseness is achieved through under-specification rather than efficient density, so it is minimally viable rather than well-structured.

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. However, for a zero-annotation mutation tool with three required, entirely undocumented parameters, the description omits nearly everything an agent needs to invoke it safely and 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 description coverage is 0% and all three parameters (task_id, request_id, claim_epoch) are required, so the schema supplies no semantics at all. The description only vaguely gestures at 'exact' and 'claim', giving no hint that claim_epoch is an epoch/version guard or how request_id relates to a claim. It does not compensate for the coverage gap.

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 gives a verb (reconcile) and a target (an exact authenticated dead blocked claim) plus a MANAGER WRITE marker, so the general intent is inferable. However, 'dead blocked claim' and 'reconcile' are domain jargon that is not defined, and nothing distinguishes this from siblings such as aiworkhub_task_recover_blocked_rework or aiworkhub_task_stale_recovery_recommend. An agent cannot tell precisely what state change this performs.

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?

There is no guidance on when to use this tool versus the numerous other blocked/stale-recovery siblings, and no prerequisites or trigger conditions are stated. The 'MANAGER WRITE' prefix hints at a privileged mutation path but does not define the scenario that calls for it.

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