Create Webhook

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the handshake requirement, how webhook scope affects triggering, and lists common events. These add meaningful context beyond simply saying 'create a webhook,' even though it does not detail the success response or authentication requirements.

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?

The description is well-structured with clear sections for requirements, scope, and common events. Every sentence contributes useful information without wasted words, and the bullet points make it scannable.

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?

For a simple 3-parameter creation tool with no annotations or output schema, the description is fairly complete. It covers the key behavioral aspects (handshake, scope) and provides examples. It does not explicitly state what the API returns upon success, but the absence of an output schema makes this less critical.

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 the baseline is 3. The description adds value by specifying that endpoint_url must be HTTPS, explaining the handshake requirement, clarifying the meaning of User vs Account scope, and providing common event examples. This goes beyond the schema's brief descriptions.

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 clearly states 'Create a new webhook in Less Annoying CRM' with a specific verb and resource, distinguishing it from sibling tools like get_webhooks and delete_webhook. It also explains the purpose of webhooks (send POST requests when events occur), leaving no ambiguity about what the tool does.

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 clear context for using the tool, including requirements (HTTPS endpoint, handshake response) and scope options (User vs Account). While it does not explicitly mention alternatives like get_webhooks or delete_webhook, the create action is obviously distinct, and the practical requirements are well covered.

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