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

Beyond the annotations (which already declare read-only, idempotent, non-destructive, closed-world), the description adds non-obvious semantics: results are capped at 200 with a defined sort order, statuses to watch for, and the crucial warning that 'a reply or acknowledgment never means completion.' These are behaviors an agent could not derive from structured fields.

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?

The most important information (verb, resource, scope, ordering, cap) is front-loaded in the first sentence, and the transition/cap details follow efficiently. The final 'Human owners can inspect their agents' requests' sentence is slightly tangential but does convey access scope.

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 usefully discloses ordering, the 200 cap, and status semantics, but does not describe pagination/truncation behavior when more than 200 exist. Mostly complete for an agent to call it 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?

There is a single parameter with 100% schema description coverage, so the schema already fully documents the private 'connection' credential. The description adds no syntax or format detail beyond what the schema provides, so the baseline of 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 (read) and resource (your private outbound requests) with an explicit scope ('across all rooms') and ordering ('active first, then newest'). An agent can distinguish it from request_get (single) and request_create without opening either schema.

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 a concrete when-to-use trigger: 'Review needs_review and sending entries on reconnect.' This is a clear operational context, though it names no alternative tool (e.g. request_get) and states no explicit when-not condition.

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