mail_get_thread_context

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

With no annotations, the description adds value by noting the default inclusion of snippets and the use of email headers. However, it omits other behavioral traits such as read-only nature, authentication needs, rate limits, or pagination behavior, which are relevant but not disclosed.

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 two concise sentences with no redundant information. It front-loads the primary action and essential detail (headers, snippets). Every word contributes to understanding.

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?

The tool has 6 parameters and no output schema, requiring the description to explain return values. It does not describe the response structure (e.g., list of messages, ordering) beyond implying related messages. Pagination and limits are not addressed, leaving a gap in completeness.

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. The description does not provide additional meaning beyond the schema for any parameter—it merely restates the overall functionality. No parameter-specific elaboration is given.

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 'Get' and identifies the resource as 'related messages in the same thread context'. It clarifies the mechanism (Message-ID/References/In-Reply-To), which distinguishes it from sibling tools like mail_get_message or mail_list_messages that do not assemble thread context.

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 the tool is for retrieving thread context but does not explicitly state when to use it over alternatives. No exclusion criteria or sibling comparisons are provided, leaving the agent to infer usage from the purpose alone.

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