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

Annotations only declare readOnlyHint=false and destructiveHint=false, so they carry little. The description adds the state-machine semantics not present in the structured fields: the task must currently be escalated, and resuming re-queues it for pickup. It doesn't mention side effects such as notifications to the escalating agent or lease interactions, 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 state transition, then the precondition, then a doc link — no filler. The URL is arguably non-essential for the agent's decision but is a single trailing token.

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 mutation tool with no output schema, the description supplies what an agent needs: current state, resulting state, and when the transition is appropriate. Remaining gaps (post-resume notification behavior, whether unassign defaults on) are minor against full schema coverage.

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 all three parameters (note, task_id, unassign) are already documented in the schema. The description adds nothing new about parameter format or defaults, so the 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?

States a precise state transition: 'Move an `escalated` task back to `queued`'. The verb, source state, and destination state are all explicit, which distinguishes it from neighbors like pause_task, complete_task, or flag_needs_more_info without opening any schema.

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?

Gives clear triggering conditions — 'when the escalation reason has been addressed (context provided, blocker cleared, or the human has reviewed)'. It does not name an explicit alternative (e.g. resolve_needs_more_info or send_back_to_creator) or state when not to use it, but the context is concrete enough to act on.

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