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

Annotations only say it is a non-read-only, open-world, non-destructive write; the description adds material behavior: it returns a one-time link exposing the signing secret (never in chat), returns a connect page for chat destinations, and requires owner/admin privileges. It also clarifies the chat webhook URL is a credential that is never a tool argument, which is critical for correct invocation.

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?

Front-loaded with the usage condition and the routing decision, and every sentence carries information (event payload contents, secret handling, permissions, doc link). It is on the long side and the event-payload sentence could be trimmed, but nothing is redundant with the schema.

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 no output schema, the description explains what the caller gets back (a one-time secret link or a chat connect page), covers authorization level, points to external docs for the format and signature, and rules out the sibling that handles email notifications. An agent has everything needed to call it 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 coverage is 100%, so the baseline is 3, but the description adds conditional semantics the schema states only locally: events are required specifically for the custom destination, and the url field must never be a chat provider URL. It stops short of adding anything on sites or idempotency_key beyond what the schema already documents.

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?

The description opens with a specific verb and resource plus scope: creating a webhook that sends FlareWarden alert events to either a signed JSON endpoint or a chat destination (Slack, Discord, Google Chat, Teams). It also distinguishes itself from the sibling update_my_notifications and from list/update/test webhook tools by naming the exact operation.

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?

It states explicitly when to use it (user wants alert events delivered to their own endpoint or a chat channel) and when not to ('Not for the user's own alert emails: use update_my_notifications'). The custom-vs-chat branch is spelled out as the routing decision an agent must make.

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