Redeem from an Arbitrage product

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

Annotations already declare the write/destructive/non-idempotent profile, and the description adds value beyond them: the required Earn permission, the weight, validation constraints, and a sample success response. It still does not say whether redemption is instant or queued, or how the redeemed amount/interest is returned, which is the main behavioral gap.

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?

Front-loads purpose, then permission/weight, then validation and examples in clearly separated sections. The example response is slightly verbose but defensible given there is no output schema; overall well-structured with little waste.

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?

With no output schema present, the description usefully supplies a sample response shape and status field, plus permission and validation requirements. It is nearly complete for a 3-required-param mutation tool, with only the redemption lifecycle left implicit.

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% and each parameter already carries its own description and enum, so the description's validation bullets largely restate the schema. The example request body adds format cues (e.g., amount as '100', productId shape 'ARB-USDT-30D') but nothing substantial beyond the structured fields.

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 ('Redeem') and resource ('Term Arbitrage product'), and clearly contrasts with the sibling stake operation. An agent can distinguish this from pionex_earn_arbitrage_stake or the dual_revoke_invest tools without opening the schema.

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?

Clear context including the prerequisite chain ('productId must exist in the product list returned by fetchProducts') and permission requirement ('Requires Earn permission'). It does not, however, name explicit alternatives or when-not conditions (e.g., distinguishing from dual revoke), so it stops short of full routing guidance.

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