wp_update_woocommerce_webhook

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

With no annotations provided, the description must disclose behavioral traits on its own, but it only says 'Update'. It does not explain whether updates are partial or full, what side effects might occur, whether permissions are required, or what the response contains.

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 a single, front-loaded sentence with no filler. It effectively names the operation and resource, though its brevity borders on under-specification rather than being a model of concise completeness.

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 mutation tool with five parameters, no annotations, and no output schema, this one-line description is severely incomplete. It omits all parameter semantics, side effects, return values, and usage context, leaving the agent without enough information to invoke the tool reliably.

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 only 20% (id), and the description adds no meaning for name, topic, status, or delivery_url. It fails to compensate for the four undocumented parameters, leaving the enum on status and the uri format on delivery_url as the only semantic hints.

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 states a specific action ('Update') and a specific resource ('WooCommerce native webhook'), and 'native' helps distinguish it from custom webhook tools. However, it does not explicitly contrast with sibling tools like wp_update_custom_webhook or wp_update_form_webhook, so it falls short of full differentiation.

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?

No guidance is provided about when to use this tool instead of wp_create_woocommerce_webhook, wp_update_custom_webhook, or wp_update_form_webhook. It also omits prerequisites, constraints, and exclusions, leaving the agent to infer usage from the name alone.

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