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

Annotations already cover read-only and idempotent safety, so the bar is lower. The description adds that the thread includes full message bodies and that no tool can send email, which is useful context. It does not add details about pagination or return format, but these are minor for a single-thread fetch.

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 sentences with no filler. The primary purpose is front-loaded, and the exclusionary note is concise. Every word earns its place.

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?

For a simple read-only get operation with one parameter, the description is adequate. It covers purpose, source of the ID, and the alternative for replies. The absence of an output schema is acceptable given the nature of the tool and the explicit mention of full message bodies.

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% and the parameter is described as 'An enrollment_id from list_inbox_threads.' The description reinforces the source of the ID, which is helpful for correct invocation. It adds value beyond the schema's basic type/format declaration.

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 states a specific verb ('get') and resource ('one inbox thread') with a key qualifier ('full message bodies'), clearly distinguishing it from sibling list_inbox_threads. It is concise and unambiguous.

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?

It explicitly states when not to use the tool (for replying) and directs the agent to the dashboard inbox, an alternative. It does not explicitly contrast with list_inbox_threads, but the 'full message bodies' phrasing implies the selection context. Clear guidance overall.

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