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

The annotation only carries a boolean destructiveHint; the description converts that into concrete consequence — the message reaches a real guest and cannot be unsent — and instructs the agent to confirm before invoking. It also discloses the channel-scope limitation on DIRECT_MESSAGE, which no annotation covers.

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 tight sentences front-load the action and the irreversibility warning, with the channel constraint and the API path trailing as supplementary detail. 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?

For an irreversible mutation with no output schema, the description supplies the essential facts: who receives it, the supported modes, the channel restriction, and the irreversibility warning. Return-value details are not needed given no output schema is defined.

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%, so the baseline would be 3, but the description adds meaning beyond the schema by explaining that DIRECT_MESSAGE routes via the booking channel and is limited to Airbnb/VRBO/Booking.com leads, and that the message targets the lead's guest rather than the lead itself.

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 (send) and resource (message to the guest of a lead), and names the two delivery modes (EMAIL / DIRECT_MESSAGE) plus the channel restriction. An agent can distinguish it from hostfully_list_messages or hostfully_list_threads 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?

Gives a clear precondition (Airbnb, VRBO or Booking.com leads only) and an operating instruction (confirm the text first), which is real usage context. It does not, however, tell the agent when to prefer a new message versus posting into an existing thread via thread_uid, or what to do for non-channel leads.

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