create_webhook

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

With no annotations, the description fully discloses behavior: creates a subscription, returns the object with id, sends HTTP POST to URL, and requires HTTPS and public reachability. No contradiction.

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 with clear flow: purpose, mechanism, return, prerequisite. No fluff. Each sentence adds unique value.

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?

Comprehensive for a creation tool with 2 params and no output schema. Explains trigger, return, and duplicate avoidance. Could add error scenarios or rate limits, but not necessary for an agent to invoke 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 already covers both parameters with descriptions. The description adds valuable context: URL must be HTTPS and controlled by user, events examples like 'post.published', and purpose of events. Adds meaning beyond schema, but schema already good.

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?

Description explicitly states 'Subscribe a URL' to event notifications, clearly identifying the verb and resource. It distinguishes from siblings like list_webhooks and delete_webhook by focusing on creation.

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 explicit guidance: 'Check list_webhooks first to avoid duplicating an existing subscription.' This tells the agent when to use the tool and what to consider before invoking.

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