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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real behavior: aggregation across the Sent folder for your own replies, header-based linking, and oldest-first ordering. It doesn't discuss cost or truncation on very long threads, so not a 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?

Two compact sentences; the core behavior and the follow-up instruction are both front-loaded with no filler.

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?

No output schema exists, and the description compensates by telling the agent what comes back (uids, oldest first) and what to do next (read_message for bodies). Nothing essential for correct invocation is missing for a 3-param 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 description coverage is 100%, so uid/folder/mailbox are already documented. The description adds that the uid can be any message in the conversation, which is a mild clarification beyond the schema's 'UID of any message in the conversation'.

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 (reconstruct the whole conversation a message belongs to) plus the mechanism (Message-ID/References), which clearly separates it from list_messages/search_messages/read_message.

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?

Explicitly routes the agent to read_message on the returned uids for full bodies, establishing the two-step workflow. It doesn't say when to prefer this over search_messages, but the within-thread context is clear enough.

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