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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), but the description adds behavior they cannot express: the long-poll semantics of 'wait' returning early on a new message, and that an untouched thread reads empty yet remains waitable. It does not mention rate limits or auth expectations, so it is not a full 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?

Four tight sentences with no filler; the core read-plus-cursor instruction comes first, followed by the blocking behavior and the empty-thread edge case. 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?

With no output schema, the description should hint at the response shape; it references 'the next value from the previous answer' but never states that the answer carries messages plus a next cursor. Otherwise it covers the parameters, blocking behavior, and the empty-thread case adequately for a 4-parameter read tool.

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 the baseline is 3, but the description adds real meaning beyond the schema: 'after' is a cursor chained from the previous response's 'next' value, and 'wait' causes early return on arrival rather than only elapsing time. That is genuine value over the field descriptions.

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 ('Read messages ... using the read key') and pins down the scoping mechanism ('after a sequence number'). It is unambiguous against write-oriented siblings like aamio_send, but it never names or contrasts an alternative tool explicitly.

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 concrete operational guidance: pass the 'next' value from the previous answer as 'after', and use 'wait' to block for arriving messages. It does not state when to prefer this over siblings (e.g. aamio_receipt or aamio_presence_get), so it falls short of explicit when/when-not routing.

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