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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, but the description adds the concrete consequence: delivery is immediate by email or LinkedIn and "cannot be unsent." It also discloses that sender_id and subject fall back to the conversation's inbox/title, which is real behavioral context beyond the 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?

Three sentences, no filler, with the core action and its irreversible consequence front-loaded before the pre-call confirmation step and the default rules. Every sentence carries distinct information.

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 an irreversible send tool with full schema coverage and annotations covering the safety profile, the description supplies the operational essentials (irreversibility, confirmation requirement, sender/subject defaults). Minor omissions remain, such as what a successful send returns or whether cc/bcc apply only to email, but nothing critical is missing.

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 100%, so all seven parameters are already documented in the schema, including the defaults for sender_id and subject that the description repeats. The description adds the "Re: <conversation title>" convention but otherwise does not deepen parameter meaning, so 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 ("Send a reply in an existing inbox conversation") and constrains it to an existing conversation, which cleanly separates it from send_campaign_test and the campaign setup siblings. The delivery channels (email or LinkedIn) further pin down what the tool actually does.

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?

Gives clear operational context: use it for an *existing* conversation, and confirm recipient and message text with the user before calling. It does not explicitly name an alternative (e.g., get_conversation or update_conversation) or state when not to use it, so it stops short of a 5.

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