needfix_reopen_superseded_task_link

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

With no annotations, the description carries the full disclosure burden. It does usefully reveal the authorization requirement ('Manager-only') and the prerequisite state (the task must have been superseded), but says nothing about what reopening actually changes, whether the prior link is destroyed or restored, or what errors occur when the precondition is unmet.

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?

A single compact sentence that front-loads the permission gate ahead of the action, with no filler. It earns its brevity, though the terseness shades into under-specification rather than optimal density.

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?

This is a mutating, permission-gated tool with no annotations, no output schema, and 0% parameter coverage. One sentence cannot cover inputs, side effects, and failure modes; an agent would have to guess at both parameter semantics and the consequences of the call.

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 the description never mentions either required parameter. It gives no hint about the format of needfix_id or the expected content/purpose of reason, so the low-coverage gap is completely uncompensated.

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 names a specific verb and resource ('reopen a NeedFix') and narrows the scope with a precise qualifier ('whose exact linked task was superseded'), which meaningfully separates it from a blanket restore like needfix_restore. It does not, however, distinguish itself from the near-identical sibling aiworkhub_dashboard_needfix_reopen_superseded_task_link.

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?

The phrase 'whose exact linked task was superseded' encodes a precondition that amounts to implicit when-to-use guidance, which is better than nothing. But no alternatives are named (e.g. needfix_restore for archived cases, needfix_link_existing_task for relinking), and the duplicate sibling is not mentioned, so an agent must infer which reopen variant applies.

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