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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond that: it uses the webhook's stored URL and secret, sends a live event, returns the mock payload plus the endpoint's response, and returns 400 when no enabled events exist.

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 front-loaded sentences with no filler; each conveys distinct information (mechanism, event selection, return value, targeting). Slightly verbose but well organized.

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 present, return values need not be detailed, yet the description still summarizes them. Error condition and default targeting are covered; only webhookId's role is left implicit, but the annotations carry the safety profile.

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% (only campaignId documented), so the description must compensate. It does: it explains the `event` parameter (choose event type, defaults to first enabled event) and confirms campaignId defaults to GROWSURF_CAMPAIGN_ID. webhookId semantics are only implied, leaving a minor gap.

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 a test event), resource (webhook), and scope (on your GrowSurf program using its stored URL and secret). Clearly distinguishes it from sibling webhook CRUD tools like create/update/delete_campaign_webhook.

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?

Establishes context well: simulating an event to exercise a webhook, with the event-type selection described. It does not explicitly name alternative siblings (e.g., list_campaign_webhooks) or when-not-to-use, but the intended scenario is clear.

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