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

With no annotations provided, the description does carry one genuine disclosure of its own: 'Read-only,' which tells the agent this is a safe retrieval operation. It stops there, saying nothing about access prerequisites, message ordering or volume, or whether a missing thread errors versus returns empty.

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 short fragments that waste no words, with the content of the response front-loaded before the safety note. The telegraphic fragments are efficient but border on under-specification rather than polished structure.

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 and no annotations, the description must carry the full load, yet it never explains what a thread object contains, where thread_id comes from, or how messages are ordered. For the only required parameter being undocumented, this leaves real gaps.

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 0% and the single parameter thread_id has no description in either the schema or the description. The description does not explain the ID's format, that it is required, or where to obtain it (e.g., from list_campaign_threads), so the agent must infer all of that.

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 resource and scope: one conversation including all messages from AI, human, and contact participants. The name plus 'One conversation with all messages' implicitly distinguishes it from the sibling list_campaign_threads, but no sibling is named explicitly and the verb is only implied by the tool name.

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?

There is no statement of when to use this versus list_campaign_threads (to find a thread_id), get_campaign_email (single email), or reply_in_campaign_thread (to respond). Usage is inferable only from the phrase 'One conversation'.

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