Refund POS Sale

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

Discloses irreversibility ('This action is irreversible') and effect on customer payment method, adding context beyond destructiveHint annotation. No contradiction with annotations.

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 concise sentences in English with efficient Spanish translation. No extraneous information.

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?

Covers key aspects: refund scope, irreversibility, confirmation requirement, partial refund option. Output schema exists, so return info is not needed. Minimal gap.

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 coverage is 100%, so description adds limited value beyond summarizing confirm and amountCents. Provide some explanation but largely redundant.

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 'Refund a POS sale in full or partially', using a specific verb and resource. It distinguishes from sibling tool 'refund_deposit' by targeting POS sales only.

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?

Explicitly mentions required parameter confirm=true and optional amountCents for partial refund. Lacks explicit comparison to other refund tools but provides clear context for use.

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