Create Webhook

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

Beyond annotations (destructiveHint=true), the description adds critical behavioral details: 'The response includes a signing secret that is ONLY shown once — save it immediately' and the limit of 5 webhooks per org. These go beyond what annotations provide, fully informing the agent of key side effects.

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 concise sentences: first states purpose, second warns about the one-time secret, third lists constraints. No redundant information; every sentence adds 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?

Given the presence of annotations and output schema, the description covers the main gotchas (one-time secret, limits, URL requirement). It omits parameter explanations but the schema and sibling tool list_webhook_event_types help. It does not mention authorization requirements or whether the webhook is immediately active.

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 does not explain any parameter individually despite 0% schema description coverage. Only the URL constraint ('URL must be HTTPS') adds some meaning to the 'url' parameter, but other parameters like event_types, org_uuid, request_id remain unexplained.

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 Automox webhook subscription', using a specific verb (Create) and resource (webhook subscription). It distinguishes from siblings like list_webhooks, update_webhook, 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?

The description provides contextual guidance such as 'Max 5 webhooks per organization' and 'URL must be HTTPS', which inform when and how to use the tool. However, it does not explicitly mention when to avoid using it or suggest alternative tools like list_webhooks to check limits.

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