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

Annotations declare destructiveHint=true and idempotentHint=false, but the description never explains what is consumed/destroyed by attesting or what happens on a repeat ack of the same batch. It does add real context the annotations lack (eligibility rules, no room response emitted), but the destructive and non-idempotent implications an agent most needs are left unexplained.

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, front-loaded with the action and scope, followed by exclusions. The eligibility sentence partially duplicates the batch_id schema description ('Wake hints and incomplete pages are ineligible'), costing a point for redundancy.

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?

There is no output schema, and the description never says what an ack returns or how failures surface for an ineligible batch. For a non-idempotent, destructive mutation, that plus the undocumented file_ids leaves meaningful gaps, though the core action and scope are adequately covered.

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 67%: room_id and batch_id are documented, while file_ids has no schema description. The description adds only that file_ids are 'delivered file-version IDs', which is useful but thin, and it does not clarify whether file_ids narrows or expands the attested scope. Baseline 3 fits given the schema carries most of the load.

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+resource: records read attestation for a consumed batch identified by batch_id, with optional file-version IDs. It also excludes a neighboring behavior ('Does not create a room response'), which separates it from reply/send_message. It does not explicitly distinguish itself from ack_wake_task, 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?

Gives clear eligibility conditions: the batch must be fully delivered and consumed, and truncated results or passive context reads are ineligible. It never names an alternative tool or says what to do when ineligible, so the routing guidance is implicit rather than explicit.

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