sibs_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 does mention the full-vs-partial refund behavior, but it does not disclose that this is a financial mutation with likely irreversible consequences, nor does it address duplicate refunds, idempotency, permissions, or outcome reporting.

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 a single sentence that is front-loaded with the core action and immediately provides the key usage distinction. There is no redundant or filler content.

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 simple refund call, the required parameter and the amount omission rule are covered. However, with no output schema and no annotations, an agent cannot anticipate response structure, error conditions, or side effects, leaving the description adequate but not fully complete.

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 transactionId, amount, and currency. The description adds little beyond restating the amount behavior already present in the schema, so it meets but does not exceed the baseline.

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 SIBS payment'), making it easy to distinguish from siblings like sibs_capture_payment or sibs_cancel_payment. The verb and object are specific and unambiguous.

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 gives clear invocation guidance: omit amount for a full refund, or provide a partial amount in minor units. However, it does not explicitly explain when refund should be chosen over alternatives or mention any preconditions, though the refund context is implied.

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