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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds mechanics the annotations cannot convey: the refund is full-only, the money leaves the business's Stripe balance, the buyer is credited, the order is marked refunded, and the action is irreversible. The required user confirmation is an additional behavioral constraint.

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?

Every sentence carries information and the irreversibility plus confirmation requirement are stated plainly. However, it opens on a two-sentence domain preamble rather than front-loading the action, which slightly delays the key fact that this performs a full Stripe refund.

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 mutation with no output schema, the description covers the funds flow, the resulting order state, irreversibility, and the confirmation prerequisite, while retry/idempotency semantics are handled in the schema. Nothing an agent needs to call it safely is missing.

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 orderId, workspaceId and idempotencyKey are each fully documented in the schema. The description adds no parameter-level detail beyond implying the order/buyer/amount, so the baseline of 3 is appropriate.

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?

States a specific verb (refund) and resource (store order) plus the scope constraint (IN FULL, business's own Stripe account). The domain framing ('link-in-bio store in Ignix', not a chat purchase) makes it easy to distinguish from the many sibling store tools like create_store_product or update_store_product.

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?

Clearly scopes when this applies (only the business's own store, where customers paid into the business's Stripe account) and imposes an explicit precondition: confirm the order, buyer and amount with the user first. It does not name alternatives, but there is no competing refund tool in the sibling list, so no routing ambiguity remains.

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