get_conversation

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

Goes well beyond the readOnly/idempotent/non-destructive annotations by describing the underlying mechanism on Gmail (X-GM-THRID across All Mail) versus other providers (Message-ID/In-Reply-To/References across inbox, sent, archive, all-mail, drafts), noting that the user's own replies are included, and disclosing that only envelopes are returned, no bodies.

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 core behavior and the read_email hand-off are front-loaded in the first paragraph, with provider-specific mechanics after. The Args block is slightly redundant in restating parameter names, but each line adds a semantic detail that the schema does not have.

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?

An output schema exists, so return values need not be explained, yet the description still flags the envelope-only return, which directly shapes downstream tool choice. With four params, empty schema descriptions, and a non-trivial provider-dependent thread algorithm, the description supplies everything an agent needs 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?

Schema description coverage is 0%, so the description carries the full burden and does so: `account` is sourced from list_accounts, `message_id` is the Message-ID header including angle brackets, and `folder`/`uid` are paired for seed identification. This is exactly the syntax detail the empty schema lacks.

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 concrete verb and resource ('return every message in the same conversation as a given message, oldest first') with an ordering guarantee. It is clearly distinguishable from siblings like search_messages and read_email, and even notes the alternative tool by name.

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 instructs the agent to use read_email for message content, and tells it how to seed the lookup via either `message_id` or `folder` + `uid`. It lacks broader when-not-to-use guidance (e.g. when a simple search would suffice), but the content/thread routing is clear.

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