isw_initiate_refund

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

Labels as 'high-risk write operation' and specifies confirm requirement. No annotations provided, so description carries full burden; lacks details on side effects or idempotency.

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?

Two sentences, front-loaded with purpose, no extraneous detail.

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 8 parameters and no output schema, description lacks details on return values, error handling, or prerequisites beyond 'settled transaction'.

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 38%; description only reiterates confirm requirement. Does not explain other parameters like refundRef, reason, extra, or merchantCode.

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?

Clearly states verb 'Initiate' and resource 'a refund for a settled transaction'. Differentiates from sibling 'isw_get_refund_status' by focusing on initiation, not status checking.

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?

Mentions requirement for confirm: true and risk level, but does not specify when to use versus alternatives or any prerequisites beyond settled transaction.

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