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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds the meaningful effect (a pending trigger is removed, and only before the delay elapses), but says nothing about permissions, what happens if no trigger is pending, or error behaviour.

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, front-loaded with the action and its timing constraint. The trailing 'Returns { success, message }' is largely redundant given an output schema exists, which keeps it out of 5 territory.

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 an output schema and rich annotations, the missing pieces are narrower: the participant-identifier choice and the no-pending-trigger / error case. For a destructive mutation tool, that leaves an agent guessing on inputs even though the effect and safety profile are covered.

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 only 33% and the description does not compensate: it never explains the participantId/participantEmail anyOf, which is the key input decision. The campaignId fallback it restates is already worded in the schema itself, so it adds no new meaning.

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: cancelling a pending delayed referral trigger, with the timing constraint ('before the delay elapses'). The 'delayed referral trigger' framing distinguishes it from the sibling growsurf_trigger_referral, which creates rather than cancels triggers.

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 one motivating scenario ('e.g. on refund/cancellation'), which implies when to reach for it, but names no alternatives, prerequisites, or when-not conditions. An agent still has to infer the boundary between this and growsurf_refund_transaction or growsurf_trigger_referral.

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