Create a webhook endpoint

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

Beyond the annotations (write, open-world, non-idempotent, non-destructive), the description adds two genuinely useful behavioural facts: the returned endpoint omits its signing secret, and the secret comes from the dashboard. The required scope is also disclosed. No mention of rate limits or what happens to duplicate URLs.

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?

Three short sentences, front-loaded with the action and scoping information. The fragments "which is copied from the dashboard" and "Needs webhooks:write." are terse but earn their place.

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 partly covers the return value (endpoint without secret) but not what the endpoint object looks like or how to retrieve the secret later. For a mutation tool that needs the schema to carry most parameter detail, this is adequate but leaves gaps around event types and duplicate endpoints.

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 67%, with isActive and eventTypes already documented in the schema. The description adds only that the URL must be HTTPS and under the caller's control, which the pattern regex largely enforces already; it says nothing about valid event type names.

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 first sentence states a concrete verb and resource: sending tracked events to an HTTPS URL the caller controls, which is what creating a webhook endpoint means. It implicitly separates itself from update_webhook/delete_webhook, though it never names a sibling.

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?

"Needs webhooks:write" gives a real prerequisite, but there is no statement of when to prefer this over update_webhook, or when not to create an endpoint at all. Usage is only implied by the tool's name.

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