orders_refund

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

No annotations provided, so the description must disclose behavioral traits. It only mentions the refund action and revoke effect, but omits side effects, idempotency, permissions required, or what happens to the order status. This is insufficient for safe invocation.

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, no filler, front-loaded with the core action. Every word earns its place.

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?

Missing output schema and no description of return value, error cases, or prerequisites. For a 3-parameter tool, the description leaves significant gaps that could lead to incorrect usage.

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 33% (only packageName described). The description adds meaning for revoke by explaining it cancels entitlements, but orderId remains unexplained, and packageName is already clear from schema. Partial compensation.

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 states 'Refund an order' with a specific verb and resource, clearly distinguishing it from siblings like orders_get and purchases_subscriptions_v2_revoke. The optional revoke parameter is explained, adding nuance.

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 a hint about using revoke but does not explicitly state when to use this tool versus alternatives like purchases_subscriptions_v2_revoke or external_transactions_refund. No exclusion criteria or contextual guidance.

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