wp_woocommerce_update_payment_gateway

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool can enable, disable, or configure a gateway, but does not disclose consequences such as partial updates, merging behavior of options, requirement that the gateway already exists, or any side effects on WooCommerce settings. For a mutation tool, this is a significant transparency gap.

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 one short sentence with the action front-loaded. It is concise and free of fluff. However, it omits essential context that could be integrated without bloating the text, so it is efficient but not a model of completeness-plus-concision.

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 five parameters, a nested options object, and no output schema or annotations, the description is insufficiently complete. It does not explain how to obtain a valid gateway ID, what 'configure' entails for the options object, whether the update is partial or full, or what success/failure looks like. The sibling listing tool exists but is not referenced, so an agent must infer the necessary prerequisite steps.

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 100%, so the baseline is 3. The description adds no field-level meaning beyond the schema's own parameter descriptions, but because the schema already documents all five parameters clearly, the description does not need to compensate. It neither harms nor meaningfully enriches parameter understanding.

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 verb ('Enable/disable or configure') and a clear resource ('WooCommerce payment gateway'). It is unambiguous about the tool's function and implies per-gateway targeting via ID, distinguishing it from broader settings tools. However, it does not explicitly call out the sibling listing tool wp_woocommerce_payment_gateways, so it misses the full sibling differentiation that would earn a 5.

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?

There is no guidance about when to use this tool versus alternatives such as wp_woocommerce_payment_gateways (for reading gateways), wp_woocommerce_update_settings, or other configuration tools. The description does not mention prerequisites like needing an existing gateway ID, nor does it state when this tool is the right choice. No exclusions or conditional context are provided.

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