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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuine context: the thread includes scheduled and unsent drafts, AI drafts awaiting review are flagged isDraft, and a human may also send from the app. It does not mention pagination or ordering limits, so it stops short of a 5.

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?

Front-loads the return description, then uses the middle sentences for tool routing, which earns its place. Slightly long at four sentences with some parenthetical overlap ('or a human sends it from the app'), but 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 carries the burden of explaining returns and does so well (thread ordering, direction, status, isDraft marker). It leaves return shape details such as pagination or per-message fields unspecified, but is sufficient for correct invocation.

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?

Only one parameter with 100% schema coverage; the schema already documents 'id' as the numeric lead ID. The description adds no format or sourcing detail beyond what the schema provides, so the 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 ('Returns a lead's full email thread') and details its composition (outbound sent/scheduled/unsent drafts plus inbound replies with direction and status). An agent can distinguish this from get_lead (single-lead details) and list_replies without opening either schema.

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?

Explicitly routes to alternatives with conditions: edit AI drafts with update_reply_draft, send them with send_reply_draft, and write a fresh answer with send_reply using the inbound reply's id. Ends with the purpose statement 'read the back-and-forth with one lead before deciding what to do next.'

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