get_email_thread

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

No annotations provided, so the description carries the full burden. It doesn't disclose whether this only retrieves one provider's threads, pagination behavior, ordering of emails, or whether it requires prior access/auth to the account. For a read tool with zero annotations, this is sparse.

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 a single short sentence with no wasted words, which is good for conciseness. However, it is under-specified rather than efficiently concise - it could add value in the same space.

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?

This is a simple 2-param read operation with an output schema present, so complexity is low. However, with no annotations and no guidance on thread semantics (ordering, filtering, multithread handling), the description is minimally adequate but leaves room for agent confusion about scope and format.

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 100%, so the baseline is 3. Both parameters (account, thread_id) have adequate schema descriptions. The description adds no new param meaning beyond 'get all emails in a conversation thread'.

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 'Get all emails in a conversation thread' states a specific verb+resource (get emails in a thread). It is clear but does not distinguish from siblings like get_inbox, get_all_unread_emails, or get_email_summary, though the thread-specific scope is somewhat implicit in the name and description.

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 vs alternatives like get_inbox, get_all_unread_emails, search_all_emails, or get_email_summary. The context is clearly thread-based, but there are no exclusions or explicit when/when-not statements.

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