create_webhook

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

Discloses that this creates a new webhook, events are optional and can attach in same call, headers have limits. Lacks mention of error behavior (e.g., duplicate endpoint) but is otherwise transparent. No annotations to contradict.

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 sentences, each earning its place: purpose, usage condition, events detail, caution. No filler, well-structured and front-loaded.

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?

Covers parameters and usage well, but there is no output schema and description does not explain what is returned (e.g., created webhook object). This omission, given complexity and no output schema, makes it slightly incomplete.

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 baseline is 3. Description adds significant value: explains events' optionality and attachment, headers limits and examples, endpoint format. Extra context raises score.

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?

Explicitly states 'Register a NEW webhook endpoint' with a specific verb and resource. Distinguishes from siblings like get_webhooks and attach_agent_webhook by specifying the condition for use.

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?

Provides clear when-to-use (only for new URLs) and when-not-to (already registered, use get_webhooks then attach_agent_webhook). Also gives explicit guidance on events: never guess/default, ask user if unspecified.

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