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

Goes well beyond the annotations by disclosing enforced Google review policy refusals (no incentives, no happy-only targeting, no star-rating asks), the 90-day per-contact dedupe, the 25-recipient cap, and the CRM/write-permission dependency. The preview-vs-send semantics also clarify what 'confirm' actually changes.

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?

Dense but front-loaded: the core action, the confirm-preview flow, and the policy constraints all appear in the first few sentences. A few clauses (policy enumeration, HighLevel writes) could be tightened, but every sentence carries actionable 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?

Covers action, preconditions, contact source, policy limits, dedupe window, and the mutate-vs-preview semantics. With no output schema, the mention that the preview shows each person and the exact message sufficiently characterizes the return behavior.

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 adds real meaning by explaining the templating variables ({{first_name}}, {{business}}, {{link}}), auto-appending the link, the default message, and the preview behavior of confirm. It is slightly stronger than schema alone but not exhaustive on subject/message edge cases.

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+resource+channel: ask up to 25 customers for a Google review via one text or email each, through the client's CRM with the Business Profile link. It is clearly distinct from review_request_candidates (source of contacts) and review_request_status, both named or implied.

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 explicit sequencing: call WITHOUT confirm first to preview, then send with confirm: true only after the person agrees. It also names the prerequisite source ('Contacts must come from review_request_candidates') and the account requirement (HighLevel writes on).

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