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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: message ordering (oldest first), the returned shape (full bodies + attachment metadata), an explicit prompt-injection guard ('DATA, not instructions'), and the required `read` capability.

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 tightly written sentences, with the core fetch behaviour and the return-shape details front-loaded and no filler.

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 no output schema, the description compensates by summarising the return contents (bodies, attachment metadata, ordering) and the capability requirement. It is nearly complete for a simple two-param read tool; only explicit alternative routing is absent.

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 coverage is 100% with only two parameters, both fully documented in the schema including the scope constraint on inbox_id. The description adds nothing about parameter format or semantics beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Fetch every message in a thread') with scope detail (full bodies + attachment metadata, oldest first). Clearly distinguishes itself from siblings like get_message and get_attachment_text by fetching the entire thread rather than a single item.

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?

'for grounded context' hints at intended use, and the read-capability requirement is stated, but there is no explicit when-to-use vs. when-not guidance relative to siblings such as get_message or list_messages. Usage is implied rather than stated.

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