wp_create_woocommerce_webhook

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

With no annotations, the description carries the full behavioral burden and it delivers two non-obvious facts: 'Secret returned once' warns the agent the credential is unrecoverable after creation, and confirm:true being required in safe mode flags a conditional execution barrier. It doesn't cover response structure or permissions, but the highest-risk behaviors are disclosed.

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 sentences with zero filler: the core action is front-loaded, followed by the one-time-security warning and the conditional requirement. Every sentence earns its place, though the confirm sentence partially duplicates the schema.

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 mutating tool with no annotations and no output schema, it covers the two operational must-knows (one-time secret, safe-mode confirmation) but doesn't state what the response contains beyond the secret or how to subsequently locate the webhook (wp_list_woocommerce_webhooks). The 'safe mode' concept is referenced without explanation, but the critical call-time behaviors are present.

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 description coverage is 80%, so the schema is doing most of the work; the description only reinforces the confirm parameter's safe-mode requirement already stated in the schema ('Required when safe mode is enabled'). It adds no new per-parameter detail beyond what structured fields provide.

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?

States a specific verb and resource ('Create a WooCommerce native webhook') that distinguishes it from sibling creation tools like wp_create_custom_webhook and wp_create_form_webhook. The qualifier 'native' precisely scopes the resource type, so an agent can tell this apart from other webhook-creation siblings.

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 'WooCommerce native' qualifier implies the domain for this tool, but there is no explicit when-to-use or when-not-to-use guidance. It never names the alternative (e.g., wp_create_custom_webhook for non-native workflows) nor states the condition that selects between them, leaving the choice to inference.

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