get_thread_messages

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

In the absence of annotations, the description provides limited behavioral context. It indicates the tool returns sender, content, and timestamps but does not mention error conditions, rate limits, or any side effects. Annotations are missing, but the description does not fully compensate.

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 concise and well-structured: a one-line summary followed by parameter details in an Args block. Every sentence adds value with no redundant information.

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?

Given an output schema exists, the description does not need to detail return values. It covers the core functionality and parameters adequately. Missing a mention of potential empty results or error handling, but overall sufficient for a read-only retrieval tool.

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?

With 0% schema description coverage, the description adds significant value by explaining each parameter: thread_id is from list_threads, limit has range and default, order has asc/desc. This fully compensates for the schema's lack of descriptions.

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?

Description explicitly states 'Get all messages in an email thread,' using a specific verb and resource. This clearly distinguishes from sibling tools like list_threads (lists threads) and get_thread_metadata (metadata only).

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?

No guidance on when to use this tool versus alternatives like search_threads or get_thread_metadata. No exclusions or prerequisites mentioned beyond thread_id coming from list_threads.

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