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

The annotations already establish that this is a read-only, idempotent, non-destructive operation, so the description does not need to repeat that. It adds useful pagination/truncation context via next_calls, but omits command-specific behavior, defaults, prerequisites such as reply_context_digest, and return expectations.

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 description is two sentences, front-loaded with the core purpose, and contains no filler. The second sentence earns its place by adding a pagination behavior hint, though the overall brevity is under-specified for a 31-parameter tool.

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?

For a complex multi-command tool with 31 parameters, no output schema, and low schema description coverage, the description is far too thin. It gives only a basic read framing and one pagination hint, leaving command semantics, parameter roles, defaults, and result shape largely unexplained.

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?

The tool has 31 parameters with only 45% schema description coverage, and the required command enum is central to invocation. The description explains neither command selection nor the meaning of any input parameter, and next_calls appears to be output guidance rather than schema semantics.

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 states a read verb with a queue/mailbox resource, making the broad purpose clear and distinguishing it from mutating inbox siblings. However, it does not cover the eight command modes such as thread retrieval, message-body retrieval, attachments, and validate_reply, so the full purpose remains underspecified.

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?

The only guidance is to follow next_calls for older or truncated thread content. There is no explanation of when to use this tool versus sibling tools, and no guidance on choosing among its commands, such as list_queue, list_mailbox, get_thread, or validate_reply.

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