Create webhook

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

No annotations are provided, so the description carries the full burden, and it is exceptionally transparent. It discloses HTTPS enforcement, allowed events, the endpoint's behavior change for ORDER_STATUS_CHANGED, and the security critical fact that the signing secret is shown only once.

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 front-loaded with the core purpose and immediately covers constraints. It is longer than minimal, but every section conveys a distinct behavioral requirement, and the use of NOTE and IMPORTANT highlights critical caveats in a scannable way.

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?

Despite having no output schema, the description covers the essential context: request validation, event choices, event behavior caveats, and one-time secret handling. It could more explicitly describe the returned webhook resource, but the pointer to get_operation_schema fills most gaps.

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 single webhook parameter is documented at 100% coverage in the schema, but the description adds meaningful detail: the HTTPS requirement, allowed events, the events to prioritize, and a pointer to get_operation_schema for the exact request shape. This goes beyond the schema's generic reference to CreateWebhookRequest.

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?

Opens with 'Create a new webhook', which clearly names both the action and the resource. It distinguishes itself from sibling tools such as get_webhook, update_webhook, delete_webhook, and validate_webhook, so an agent can immediately tell this is the creation operation.

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 gives a clear context for usage: creating a webhook, requiring HTTPS, and restricting to specific events. It does not explicitly contrast with alternatives like update_webhook, but the 'new' in the first sentence makes the intended operation unambiguous.

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