getDoubleWinLeverage

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

Despite no annotations, the description fully discloses behavioral constraints: price range rules (lowerPrice < initialPrice < upperPrice, multiples of priceTickSize), and that returned leverage and expireTime are used for placing a Stake order with an expiration. Rate limit is also specified.

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 concise: a brief main sentence followed by bullet points for conditions, prerequisites, rate limit, and notes. Every sentence is valuable, no redundancy. Front-loaded with the core purpose.

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 4 required parameters, no output schema, and no annotations, the description covers prerequisites, constraints, usage instructions, and follow-up actions (placing Stake order). It also references alternative tools for other cases, providing complete context for an agent to use the tool correctly.

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 0%, but description adds meaning: it explains the relationship among lowerPrice, initialPrice, upperPrice, and mentions productId and initialPrice implicitly. It also describes constraints and their purpose. However, it could provide more detail on productId and initialPrice.

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 tool's purpose: 'Query the leverage for a Double Win RFQ product with user-selected price range.' It distinguishes from fixed-range products by specifying 'Only applicable for RFQ products' and directing to alternative sources for fixed-range products.

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?

Explicitly states when to use: 'Only applicable for RFQ products (isRfqProduct=true).' Provides alternatives: 'For fixed-range products, obtain leverage from Get Product Extra Info or the WebSocket topic.' Also includes prerequisites ('Requires Earn permission') and rate limit ('1 req/s').

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