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

Annotations only supply destructiveHint=true; the description adds the crucial real-world consequence — the message "reaches a real guest and cannot be unsent" — which is exactly the behavioral context an agent needs before an irreversible send. It omits auth/permission requirements and rate limits, so it is strong but not exhaustive.

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: purpose and channel scope first, then the irreversibility warning, then the API endpoint. Every clause carries information and nothing is padded.

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 is responsible for the operation's shape, and it covers purpose, delivery modes, audience restriction, and irreversibility. It lacks any note on what a successful call returns or how errors surface, a minor gap for a 5-parameter tool.

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 is 3. The description goes slightly beyond the schema by tying the type enum values to the delivery mechanism and by explaining that DIRECT_MESSAGE is only available for channel leads, which is semantic meaning the schema does not carry.

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 verb and resource ("Send a message to the guest of a lead") and scopes it to two delivery modes, distinguishing it from read-side siblings like hostfully_list_messages and hostfully_list_threads. The channel constraint (Airbnb, VRBO, Booking.com leads only) further narrows the purpose beyond what the name conveys.

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?

It gives clear when-to-use context: EMAIL vs DIRECT_MESSAGE, and the restriction that DIRECT_MESSAGE only works for channel leads. It also warns to confirm the text before sending. It does not explicitly name a sibling alternative (e.g., list_messages for reading threads), so it stops short of full when/when-not routing.

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