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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the base behavior is covered. The description adds useful context about returning messages ordered within each thread, but does not disclose additional side effects, rate limits, or authorization requirements beyond what annotations provide.

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 compact and well-structured: it states what the tool does, how to specify thread selection, and what the response ordering will be. No unnecessary words or redundant content are present.

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?

With an output schema present and all input parameters fully described in the schema, the description provides enough context for correct invocation. It also clarifies the single-vs-multiple thread usage and ordering behavior, so no critical operational details are missing.

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?

The input schema covers all four parameters with descriptions, and schema coverage is 100%. The main description mostly reiterates the id/ids distinction without adding deeper meaning for limit or agentId, so it does not exceed the baseline set by the schema.

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 clearly states the tool fetches all email messages in one or more threads, using a specific verb and resource. It is distinct from siblings like email_get or email_list based on the thread-scoped behavior.

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 gives clear parameter usage (id vs ids, ordering) but does not explicitly compare this tool to alternatives such as email_search or email_list. The use case is implied rather than stated with explicit when-to-use or when-not-to-use guidance.

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