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

No annotations are provided, so the description carries the full burden. It does disclose the key trait 'Read-only,' which signals a safe, non-mutating operation, and it clarifies the scope of returned data by listing the channel types. It omits edge-case behavior (e.g., missing lead, empty thread) and return format, but the central safety-relevant trait is covered.

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 sentences totaling about twenty words, with the core function front-loaded in the first sentence and the behavioral note in the second. Every word earns its place and there is zero 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?

For a simple one-parameter getter with no output schema and no annotations, the description adequately covers what is returned, the scope, and the read-only nature. The remaining gaps are the implicit id semantics and the lack of any distinguishing guidance against the similarly named sibling crm_communication_thread, which an agent would benefit from.

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?

The single parameter `id` has no schema description (0% coverage), so the description must compensate. The phrase 'with this lead' implies that id refers to a lead, which is a useful hint, but it never explicitly states 'id is the CRM lead ID' and leaves ambiguity between a lead identifier and a conversation identifier.

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 ('the full message thread with this lead on their source channel') and enumerates the channel types (LinkedIn / email / widget / telegram / phone transcript), which clearly identifies what the tool returns. The title supplies the verb 'Get.' However, it does not differentiate from sibling crm_communication_thread, which by name could plausibly return the same thing, so it falls short of full sibling distinction.

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 phrase 'full message thread with this lead' implies the use case: retrieve the complete source-channel conversation for a single lead when you need full context. But there is no explicit when-to-use versus when-not-to-use guidance, and no alternatives are named despite the closely related siblings crm_communication_thread and crm_communication_history.

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