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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description adds meaningful state-machine behavior: the flag clears and the task re-enters the queue ready to work. It doesn't mention permissions, who may answer, or what happens if the response is rejected.

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?

Two tight sentences that front-load the trigger and the outcome, plus a reference link. Nothing is wasted, though the outcome sentence could be shortened.

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?

No output schema exists, and the description compensates by stating the observable result (flag cleared, task requeued). With all parameters documented and the precondition stated, an agent has what it needs to call this 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 100%, so each of the five parameters is already documented, including task_id accepting a pasted Tango URL. The description restates the required trio and marks constraints as optional without adding format or validation detail, so baseline 3 applies.

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?

Names the trigger state ('comes back flagged needs more info'), the exact inputs to supply (goal, definition of done, optional constraints), and the resulting state change. This separates it cleanly from flag_needs_more_info, send_back_to_creator, and answer_question. It stops short of a crisp verb+resource statement up front, but the effect is unambiguous.

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 opening clause gives an explicit condition for use ('when a task you raised comes back flagged needs more info'), which is precise context. It does not mention exclusions or point to alternative tools for related situations, so it falls just short of a 5.

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