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

Goes well beyond the annotations by disclosing that unsubscribes and the suppression list are respected, and by enumerating the four return statuses including the deduplication rule ('already_requested... no second email is sent and no credit is spent'). This is meaningful side-effect and cost information for a destructive, open-world tool.

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 dense sentences with no filler: purpose first, safety gate second, return contract third. The most decision-critical information (real person, explicit user request required) is front-loaded.

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?

There is no output schema, yet the description fully enumerates the possible return statuses and their meanings, which compensates. Combined with the safety gate and dedup behavior, an agent has everything needed to call this 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 description coverage is 100%, so all three parameters (name, email, location_id) are already documented in the schema, including the 'UUID from list_locations' hint. The description adds no additional parameter-level semantics, so the baseline of 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 (send) and resource (one review-request email to a real customer) plus the delivery mechanism (ReputeMap's campaign engine). The emphasis on 'ONE' and 'a real customer' distinguishes it from the sibling drafting tools like draft_reply.

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 an explicit gating condition: 'only use it when the user explicitly asks to request a review.' It also explains why the restriction exists ('This emails a real person'), which is enough for an agent to decide when not to call it.

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