Create Webhook

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

Annotations provide no safety hints (readOnlyHint=false etc.). Description only says 'Register a new webhook endpoint' without discussing side effects, error cases, or behavior on duplicate URLs. Minimal behavioral disclosure beyond the action itself.

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?

Description is concise but includes bilingual text (English and Spanish), which adds length. Example is valuable. Front-loaded with key purpose. Could be slightly shorter by removing bilingual repetition, but still efficient.

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 output schema exists, return values are covered. The description covers required parameters, event options, and an example. Sibling tools are numerous, but the description provides enough context for an agent to select this tool appropriately. Lacks mention of authentication or idempotency, but annotations handle those implicitly.

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 covers 100% with descriptions. Description adds an example usage with url, events, and secret, and explicitly lists all available events, providing extra context beyond the schema.

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?

Clear verb 'Register' and resource 'new webhook endpoint'. Explicitly distinguishes from sibling tools like list_webhooks, get_webhook, update_webhook, delete_webhook, test_webhook. Includes a concrete example.

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?

States required parameters (URL and events) and lists available events. Provides an example. Does not explicitly compare with update_webhook or other alternatives, but context makes it obvious when to create vs. update.

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