aiworkhub_task_reroute_launch_identity

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

No annotations are provided, so the description carries the full burden. 'COORDINATOR WRITE' usefully discloses that this is a mutation requiring coordinator privilege, but nothing is said about what state is changed, whether the pending launch is cancelled or reassigned, reversibility, or side effects on the from_runner task.

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 tight sentence with the operation class front-loaded and no filler. Effectively sized, though its brevity is partly a symptom of under-specification rather than disciplined concision.

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 no explanation, but for a 7-parameter write tool with zero annotation and zero schema-description coverage the description is far too thin. An agent cannot determine required inputs, side effects, or the correct calling context from this text.

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?

Seven parameters with 0% schema description coverage, and the description supplies no meaning for any of them. It never explains the distinction between from_runner and to_runner, what to_adapter_id or to_model select, or how topic and reason are used — failing to compensate for a total schema documentation 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?

States a specific verb (reroute) and a specific resource (one pending retry launch identity), which is more precise than a generic 'update'. The 'COORDINATOR WRITE' prefix signals the operation class. However, it does not differentiate itself from adjacent siblings like aiworkhub_task_retry_terminal or aiworkhub_task_queue_request, leaving the agent to guess which routing-related tool applies.

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 word 'explicitly' hints the reroute must be user-directed rather than automatic, but the description never states when to use this tool versus alternatives such as retry_terminal or stale_recovery_recommend. No preconditions, no exclusions, no named alternatives.

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