ghl_conversation_update_email_message_status

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

Annotations indicate mutation (readOnlyHint=false) and idempotency (idempotentHint=true). The description adds behavioral context: requires OAuth scope, provider ownership, and explains additive event merging and recipient status upserting. It does not contradict annotations.

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?

The description is verbose with multiple paragraphs covering authorization, field details, and inference rules. While well-structured with sections, it could be more concise; the first sentence effectively summarizes the purpose.

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?

Given the complexity (two parameters, nested objects, no output schema), the description is thorough: it covers authorization, field semantics, provider restrictions, and update behavior (additive/upsert). It is nearly complete for an agent to use the tool correctly.

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 good descriptions, but the description adds extra value by explaining inference rules, additive merging, and the distinction between events and recipients. This goes beyond the schema to clarify parameter usage.

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 title and description clearly state the tool updates email message status, including delivery events, per-recipient statuses, and overall status for custom conversation provider emails. It is distinct from sibling tools like ghl_conversation_update_message_status due to the 'email' specificity.

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 description specifies that the tool is for emails sent via a custom conversation provider and warns that attempts on LC Email or Mailgun emails return 403. This provides when-to-use and when-not-to-use guidance, though it does not explicitly name alternative tools.

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