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

No annotations are provided, so the description carries the full burden and does so: it discloses the outbound email side effect, the exact gate (sendApproval:true plus smtpUser/smtpPassword), the default-safe behavior, three separate rate limits (5/run, 20s interval, 20/day), auth requirement, facade limit, and pricing. This is materially more than the schema exposes.

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?

One dense paragraph, front-loaded with purpose then alternatives then side effects then auth/pricing — a sensible priority order with no filler sentences. It is long, and the sendApproval gate is restated in both the description and the schema, which is mild redundancy rather than waste.

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 15-parameter tool with no annotations and no output schema, the description covers returns ('pitch text and a shareable report URL'), the destructive/outbound path, credentials, limits, and cost. The mode enum's two behaviors (generate vs check-engagement) are left entirely to the schema, which is the only real gap.

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 the baseline is 3, but the description adds semantics the schema states only locally — that maxEmailsPerRun is bounded by an inter-send delay and a global daily cap, and that the SMTP path only activates under an explicit approval gate. It adds value beyond the field-level text without fully re-documenting all 15 parameters.

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?

Starts with a specific verb+resource pair ('Generate pre-sales reports from a business's worst Google Maps reviews') and immediately distinguishes the output (HTML report plus ready-to-send pitch). It also names three sibling tools it is NOT (review_radar, local_presence_audit, google_maps_scraper), so an agent can route without opening a 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?

Explicit when-to-use ('agency outbound... show prospects their visible bad reviews') and three explicit when-not cases with the alternative tool named for each. Nothing is left to inference about selection against siblings.

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