wordpress_wc_get_payment_gateways

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Get' which implies a read operation, but does not disclose what the return value contains (e.g., list of gateway IDs, settings, enabled status), any side effects, or error conditions. This is insufficient for a zero-parameter tool with no output schema.

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 extremely concise—only five words—and is front-loaded with the verb. It avoids unnecessary fluff and is easily scannable. However, it is so brief that it borders on under-specification, though it remains a complete, clear phrase.

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 that there is no output schema, the description should explain what the tool returns (e.g., a list of payment gateways, including enabled/disabled states, titles, and IDs). It does not. The tool is simple, but this lack of return information leaves the agent uncertain about the tool's output, making it incomplete.

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 tool has zero parameters, so the baseline score is 4. There is no parameter information to add, and the description correctly includes none. The schema already captures the absence of parameters, so no additional semantics are needed.

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 the action ('Get') and the resource ('WooCommerce payment gateways'). It is specific and distinct from sibling tools that retrieve other WooCommerce entities (products, orders, customers), leaving no ambiguity about its purpose.

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 no guidance on when to use this tool vs alternatives, nor does it mention any prerequisites or exclusions. For a simple getter, this is a minor gap, but the lack of any context beyond the basic action means the agent receives no help in deciding between this and other retrieval tools.

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