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

Annotations declare only the generic write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); they say nothing about consent, privacy, or outcome. The description adds all three: the consent gate, the instruction to strip contacts' names, phone numbers and message text, and the return shape { received: true } — none of which is derivable from 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?

Four sentences, each load-bearing: purpose, triggers, consent precondition, content rules, then return value. The consent requirement is front-loaded in the same sentence as the triggers, so the agent cannot act before reading it.

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 a two-parameter, non-destructive write with no output schema, everything needed to call it correctly is present: when to offer it, that user agreement is required first, what to put in and leave out of the message, and what comes back.

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 earns an extra point by adding content rules for `message` (write in the user's own words, omit PII unless asked). It does not advise how to choose a `category` from the enum, which keeps it off a 5.

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 names a specific verb and destination: 'Pass a message from the user to the DripRaven team.' This immediately distinguishes it from every sibling (campaign, contact, template and billing operations), which are all product actions rather than a channel to the vendor.

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 three explicit trigger conditions (capability gap, unsolvable problem, sentiment) plus a hard precondition: 'only call it once the user has agreed to send it.' That is a clear when-to-use and when-not-to-act rule, not an implied one.

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