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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful disclosure of what each row contains (subject, participants, message count, unread count, muted status), but says nothing about ordering, pagination, or behavior when the folder does not exist.

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 short sentences with the content summary first and the usage cue second; no filler. The informal wording ('single letters', 'the thread that will not stop') is colorful but still readable and does not obscure the meaning.

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?

Since there is no output schema, the description usefully documents the shape of returned thread entries, which is a real contribution. It is still incomplete for a 3-parameter tool: the limit (capped at 50) and the mailbox/folder relationship are never explained, leaving the agent to guess at scoping and page size.

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 only 33% (only 'folder' has a description noting the INBOX default), and the description adds no parameter meaning at all: it never mentions limit, mailbox, or folder semantics. With low coverage the description should compensate but instead leaves two parameters entirely unexplained in both places.

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 states the resource (conversations/threads in a folder) and explicitly contrasts it with single-message listing ('rather than single letters'), which distinguishes it from mail_list_messages. The verb is implied rather than stated, but the enumerated return fields (subject, participants, message count, unread count, muted) make the operation unambiguous.

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?

'Use before answering a long back-and-forth, or to find the thread that will not stop' gives genuine situational guidance for when threads beat messages. However, it names no alternative tool and gives no exclusions, so the agent must infer that mail_get_thread is the follow-up for a chosen thread.

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