Create Webhook

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

The description discloses that the signing secret is returned once and appears in the conversation log, advising to treat logs as sensitive. This adds value beyond the annotations, which only indicate idempotency.

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 sentences, front-loaded with purpose, no redundant information. Every sentence is essential.

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?

Given the output schema exists, the description adequately covers the critical behavioral aspect (secret handling). Could mention events or url constraints, but schema partially covers them.

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?

The description adds no parameter-specific information. The input schema covers 25% of parameters with descriptions (only idempotency_key), yet the description misses explaining url, events, and description 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?

The description 'Create a webhook endpoint' is a specific verb+resource, clearly distinguishing it from sibling tools like delete_webhook, update_webhook, etc.

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?

The description provides important post-creation guidance about handling the signing secret, but does not explicitly state when to use this tool versus alternatives like update_webhook or test_webhook.

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