BinanceGetSolRedemptionHistory

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

No annotations are provided, so the description carries the full burden. It only states the basic retrieval action and the fields returned (amount, exchange rate). It does not disclose pagination behavior, time-range handling, authentication requirements, or any rate limits or edge cases, which are crucial without 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?

Description is a single, clear sentence with no redundant words. It is appropriately sized and front-loaded with the core purpose and key output details.

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 the tool has 5 parameters (all optional), no output schema, and no annotations, the description provides minimal context. It explains the purpose and the type of data returned, but does not clarify pagination semantics, time-range filtering, or what the response structure looks like. However, the schema descriptions cover the parameters, so the description is adequate for a simple history retrieval tool but not comprehensive.

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 the baseline is 3. The description does not add any meaning about parameters beyond what the schema already provides (size, current, startTime, endTime, recvWindow). It neither enhances nor contradicts schema info.

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?

Clear, specific verb+resource+scope. States it retrieves SOL redemption history and details the amount of BNSOL redeemed for SOL and the exchange rate. Differentiates from sibling tools like BinanceGetEthRedemptionHistory by explicitly targeting SOL.

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?

No guidance on when to use this tool versus alternatives. The description does not mention alternative tools (e.g., for ETH redemption history) or any exclusions. It simply states what the API allows, leaving usage context implied.

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