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

Annotations declare readOnlyHint=false and idempotentHint=false, and the description explains why: it 'records pickup, not read acknowledgment', which is a genuine side effect an agent must know about. It also discloses the pagination mechanism (frozen JSON fragments plus next_cursor) and the eligibility precondition (complete delivery). It does not say whether pickup is reversible or what authorization is required beyond the schema's OAuth note.

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?

Three tight sentences with no filler, and the payload inventory is front-loaded so an agent knows the return shape immediately. The jargon ('frozen JSON fragments', 'eligible batch_id') is dense but each clause carries information.

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?

With no output schema, the description carries the burden of describing returns, and it does list the payload components and the next_cursor continuation. It leaves open what a 'Brief' is, how truncated fragments are reassembled, and which tool consumes the batch_id. For a three-parameter read tool this is nearly sufficient, but those gaps keep it below a 5.

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 all three parameters are already documented, including the max_chars/max_pages relationship to batch eligibility. The description reinforces the 'bounded batch' idea but adds no format, default, or tuning guidance beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

The description names a concrete verb and enumerates the resources returned: new messages, Brief and changes, accepted/pending decisions, file-version metadata, and teammates. That is far more specific than a tautology. It never distinguishes itself from the confusingly similar sibling `catch_up`, nor from `room_situation` or `wait_for_messages`, so it stops short of a 5.

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?

Usage is only implied: 'bounded batch' and 'batch eligibility requires complete delivery' hint at when this is appropriate, and 'records pickup' hints at the commit semantics. There is no explicit statement of when to choose this over `catch_up`, `room_situation`, or `wait_for_messages`, and no stated prerequisites or exclusions.

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