gold_create_refund

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

With no annotations provided, the description carries the full disclosure burden and does add two meaningful traits: 'Destructive' and 'BYOK fail-closed'. However, it does not explain what is affected (e.g., order state, payment reversal) or that a CONFIRM gate exists, so the disclosure is useful but terse.

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 definition is short and front-loads the action, endpoint, and safety warnings. However, 'Gold PRO $29' is a wasted fragment unrelated to invocation, keeping it from being tightly structured.

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 destructive operation with 7 parameters, no output schema, and no annotations, this is too thin. It omits the CONFIRM requirement, the operational effects of a refund, and the meaning of the flag parameters, leaving an agent to guess at safe invocation.

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 14% (confirm has a description), yet the description says nothing about order_id, amount, reason, api_refund, refund_payment, or line_items. The endpoint implies the WooCommerce refund contract but gives the agent no semantics for the boolean toggles or amount formatting.

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?

'create refund via POST /wp-json/wc/v3/refunds' names a specific verb and resource, and no sibling tool is refund-related, so the agent can distinguish it without opening the schema. The 'Gold PRO $29' prefix is irrelevant noise but does not obscure the action.

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 when-to-use guidance or alternatives are given. An agent cannot determine when this tool should be preferred over siblings such as gold_update_order_status or gold_wc_batch, and no prerequisites or ordering constraints are mentioned.

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