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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context by stating it returns all messages in a conversation and explaining how thread membership is determined (Gmail thread id or References headers). It does not mention ordering or pagination, but this is a minor gap for a read-only listing operation.

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?

A single, well-structured sentence that leads with the action and resource, then provides the key implementation detail about thread identification. There is no filler, and every element earns its place.

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 read-only conversation-listing tool with annotations covering safety, the description covers the core behavior and the critical cross-system distinction (Gmail thread id vs References headers). It lacks an explicit statement about output ordering, pagination, or limits, and it could more clearly say that uid is a message identifier rather than a thread identifier, but overall an agent can correctly invoke it for the intended use.

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 67%, with account and folder documented in the schema but uid lacking a schema description. The description partially compensates by implying uid identifies the 'given message' whose conversation is returned, but it does not make the uid-vs-thread-id relationship explicit, and folder/account semantics are left solely to the schema. This is acceptable but not a strong compensation.

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 ('Lists') and a specific resource ('all messages belonging to the same conversation as the given message'), making the tool's function immediately clear. It also distinguishes this from single-message tools like get_message by emphasizing the thread/conversation scope, and the parenthetical on Gmail thread id vs References headers clarifies how conversation identity is resolved.

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 implies when to use the tool: when you need the full conversation around a given message rather than a single message. However, it does not explicitly name alternatives like get_message or search_messages, nor does it state when not to use this tool. The thread-id vs References distinction gives useful context but stops short of explicit routing guidance.

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