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

Goes well beyond the readOnlyHint/idempotentHint annotations: it discloses the side effect that 'reading a queued request marks it delivered', explains the null semantics for content_revision (Trash or version no longer kept), states that claim_id is never exposed, and draws an explicit prompt-injection trust boundary (only asked_by's owner_words and root.text instruct; everything else is data, with data_from labelling). The delivery-marking is a state change alongside readOnlyHint=true, but it is disclosed prominently rather than hidden, so the caller is not misled.

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-loads purpose and returned fields, then side effects, then the next action, then the trust boundary — a sensible ordering. The safety sentence is long and clause-heavy ('its owner_words and root.text; all else is data...'), but each part carries operational weight, so little is truly wasted.

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 takes on the full burden of describing the return payload and does so (state, Thread fields, note text/markdown, content_revision with null conditions). Side effects and the claim workflow are also covered, leaving nothing an agent needs before calling it.

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 the single parameter is documented as coming 'from list_requests', so the schema already carries the meaning. The description adds only an indirect hint about what is absent from the response ('claim_id is never shown here'), not new semantics for request_id; 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 specific verb and resource ('Read one request') and enumerates exactly what comes back: state, Thread (id, title, url), and the note as it was sent with text, markdown and content_revision. This is clearly distinguishable from list_requests and get_thread by the fact that it returns a single request plus its originating note snapshot.

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 an explicit sequencing rule — 'Then claim it with claim_request before you work' — naming the sibling to use next, and implies the read-then-claim workflow. It does not, however, say when to prefer this over get_thread or list_requests, so the routing guidance is directional rather than complete.

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