refund_payment

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 states the action ('refund') but doesn't explain critical behaviors: whether this is a partial or full refund by default, if it requires specific permissions, what happens on success/failure (e.g., funds reversal, status updates), or any rate limits. For a financial mutation tool, this is a significant gap in transparency.

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 with just three words, front-loading the core action without any fluff. Every word ('refund', 'a', 'payment') earns its place by directly conveying the tool's purpose, making it efficient and easy to parse.

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 the complexity of a financial refund operation, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., idempotency, error handling), usage context, and expected outcomes. For a tool that modifies payments, this minimal description fails to provide the necessary context for safe and effective use.

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 schema already documents both parameters ('pf_payment_id' and 'amount') adequately. The description doesn't add any meaning beyond this, such as explaining that 'amount' is optional for full refunds or detailing format constraints. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 ('refund') and the resource ('a payment'), which is specific and unambiguous. However, it doesn't differentiate this tool from potential sibling tools like 'cancel_subscription' or 'query_transaction' that might also involve payment modifications, leaving room for confusion about when to choose this specific refund operation.

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 versus alternatives. It doesn't mention prerequisites (e.g., payment must be in a refundable state), exclusions (e.g., cannot refund partially after a certain period), or relate it to sibling tools like 'cancel_subscription' for subscription-related refunds. This lack of context makes it hard for an agent to decide appropriately.

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