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

With no annotations, the description carries the behavioral burden and does well: it says the result includes every message with sender, recipients, date, summary, snippet, and every attachment with metadata and an attachment_id. It also warns that returned content is untrusted quoted data, which is valuable security context. It does not mention error behavior or access constraints, so it falls short of 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?

The description is two dense but well-structured sentences. The core purpose and return contents are front-loaded, and the final sentence adds a necessary security instruction without wasteful wording.

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 one-parameter read tool with no output schema and no annotations, the description is complete enough to call correctly. It explains the return contents, attachment metadata, where the ID comes from, and how to treat untrusted message content.

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 coverage is 100%, so the UUID parameter is already documented. The description adds useful meaning beyond the schema by explaining where conversation_id values originate: list_feed, get_cluster, or search.

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 uses a specific verb and resource: 'Read one conversation in full.' It immediately defines scope as every message and attachment in a single thread, which clearly distinguishes it from sibling tools like list_feed, search, and get_cluster.

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?

It states where a valid conversation_id comes from: list_feed, get_cluster, or search. That gives clear context for invoking the tool, but it does not explicitly say when not to use it or contrast it directly with alternatives such as get_cluster.

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