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

Annotations declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the agent knows this call mutates state destructively. The description, however, leads with 'Returns' and never discloses what the 'pickup' consumes, whether the offer disappears after retrieval, or how idempotent retries behave. The only behavioral nuance offered ('does not attest reading or begin the separate answer turn') is cryptic because 'answer turn' is never defined here.

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 with the core purpose front-loaded and the disambiguating constraint second — no filler. The second sentence is terse to the point of opacity ('the separate answer turn'), which costs a little clarity but not much length.

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-parameter, no-output-schema tool with full schema coverage, the description is adequate on what it returns. It is not complete on the destructive pickup semantics implied by the annotations, and it does not explain the relationship between the returned packet and the subsequent acknowledgement/answer flow, which is the main thing an agent needs to route 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%, and both parameters carry real documentation (room_id OAuth-authorized, task_id a caller-generated idempotency UUID). The description adds only that lookup happens 'by task_id'; it says nothing about the room_id authorization requirement or the retry semantics that the schema itself explains. Baseline 3 is appropriate.

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 and resource — 'Returns this participant's offered triage task packet by task_id' — with scoping ('this participant's', 'offered'). That distinguishes it from generic reads like read_message or read_file, but it never names its closest wake-cycle siblings (ack_wake_task, claim_wake, pass_wake), so full sibling differentiation is left to inference.

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 clause 'Pickup does not attest reading or begin the separate answer turn' implicitly defines the boundary of this step and points toward an acknowledgement/answer step, but it never names that tool or states a condition like 'use ack_wake_task once you have read the packet.' Usage is inferable rather than explicit, and no when-not-to-use case is given.

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