mail_read_conversation

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

Annotations already declare readOnlyHint and destructiveHint false. The description adds important behavioral details about pagination and the lack of snapshot/cross-mailbox guarantees, which complements the annotations without contradiction.

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 concise, using two sentences to convey the core action, pagination behavior, and limitations. No unnecessary words or 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?

The description explains pagination and guarantees but lacks details about the return format or fields. Since there is no output schema, the description should state what a message page contains, but it does not. It is adequate for basic usage but incomplete for fully informed calls.

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 description does not explicitly describe any parameters. While conversationId and pageSize are implicitly referenced, accountId and cursor are not mentioned, and the schema provides no per-parameter descriptions. The description adds minimal value beyond the schema patterns.

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 clearly states the tool reads one page of messages sharing a conversation ID, distinguishing it from mail_search and mail_read_message. The verb 'read' and resource 'conversation messages' are specific.

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 description provides clear guidance on pagination ('follow nextCursor') and states limitations (no snapshot, no cross-mailbox guarantee). It implies use for iterating through a conversation but does not explicitly contrast with alternatives like mail_search.

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