BinanceExtraBonusList

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

No annotations are provided, so the description must disclose behavioral traits. It only states that it 'retrieves' data, which implies a read operation, but it does not mention required permissions, rate limits, pagination behavior, or whether any side effects occur. For a retrieval tool, this sparse behavioral disclosure is insufficient.

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 a single, information-dense sentence that front-loads the verb and resource, then lists relevant bonus categories. There is no fluff or redundant phrasing.

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 8 parameters, no output schema, and no annotations, the description should explain what the returned data looks like and how to use the parameters. It lists bonus categories but does not describe the response structure, pagination behavior, or date-range semantics. While schema descriptions cover parameter syntax, the overall context for a complete API invocation is lacking.

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?

The input schema provides descriptions for all 8 parameters with 100% coverage. The description adds no additional parameter-level meaning—it focuses on the output categories. Therefore, it meets the baseline for schema coverage but adds no extra semantic value.

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 uses the specific verb 'Retrieves' and identifies the resource as 'extra bonuses related to mining activities', then enumerates distinct categories (merged mining, activity bonuses, rebates, smart pool bonuses, income transfers, pool savings). This clearly differentiates it from sibling tools like BinanceEarningsList or BinanceMiningAccountEarning, which focus on regular earnings.

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 does not explicitly state when to use this tool over alternatives, nor does it name exclusions or alternative tools. However, the specific mention of 'extra bonuses' and the list of bonus types imply that this tool is appropriate for retrieving supplementary mining rewards, providing a mild usage cue.

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