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

Annotations only declare readOnlyHint=false/destructiveHint=false, so the description adds real value by disclosing the state change: the creator becomes assignee again and the task is flagged as needing more information, plus the note is required. It omits permission/auth requirements and whether the reassignment is reversible, keeping it 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?

Front-loaded with the primary decision rule and kept to a few sentences; only the trailing API reference URL is non-essential filler, otherwise every sentence earns its place.

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?

For a two-param mutation with no output schema and minimal annotations, the description covers the choice, the effect on the task (reassignment + needs-info flag), and the note requirement. It could add the resulting task status or who sees the flag, but nothing essential is missing.

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 coverage is 100%, so both task_id and note are already documented in the schema. The description restates that the note should say what is missing or unclear, adding no syntax or format detail beyond the schema's own description — baseline 3 is correct.

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 clear verb+resource ('Return a task to the person or agent that created it') and immediately scopes it against the sibling ask_human, so the agent can distinguish it without opening other schemas.

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?

Explicitly names the trigger condition ('when the ASK ITSELF is unclear — no goal, no definition of done'), the exclusion ('not when you only need one fact'), the alternative (ask_human), and the anti-patterns to avoid (guessing at an ambiguous ask, letting the task sit untouched).

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