getSmartLeverageRedeemEstAmountList

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

Beyond readOnlyHint=true, the description discloses operational and behavioral details: 10 req/s rate limit, 10-minute server-side cache, the requirement that estRedeemAmount must match the cached value, max 5 position IDs, and per-position success/failure. No contradiction with annotations.

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 tightly structured: purpose, permission, rate limit, ordering/caching constraint, then bulleted limits. Every sentence earns its place and the critical caching/ordering warning is prominently marked 'Important'.

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 two-parameter read endpoint with no output schema, the description covers permission, rate limiting, temporal ordering, cache semantics, input cardinality limits, and per-position response behavior. Nothing essential for correct selection and invocation 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?

With 0% schema description coverage, the description compensates by adding constraints: one or more positions, max 5 IDs per request, and per-position result behavior. It does not re-explain the category enum (already in schema), but this is acceptable because the schema documents it. Some nuance about what positionIds refer to is implicit but inferable.

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 opens with a specific verb-resource pairing: 'Query the estimated redemption amount for one or more Smart Leverage / Double Win positions.' It also frames the endpoint relative to Redeem orders, making it distinguishable from execution/query siblings like executeRedeem or getEarnPosition.

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?

It gives clear when-to-use context: must be called before placing a Redeem order, and requires Earn permission. It does not explicitly name alternatives or state when not to use it, but the precondition and rate-limit context are strong enough to guide selection.

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