BinanceEarningsList

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It mentions the returned fields (transferred hashrate, daily hashrate, profit amount, payment status) but does not disclose pagination, default date ranges, or whether the list is ordered. It does not contradict annotations, but it leaves significant behavioral gaps for a read tool.

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, dense sentence that front-loads the main action ('Retrieves list of earnings') and then lists relevant data fields. Every word contributes value; there is no redundancy or filler.

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 8 parameters, no output schema, and no annotations, the description is too minimal. It lists some return fields but does not explain the overall response structure, pagination behavior, or how the date parameters (startDate/endDate) affect results. The description is incomplete for a complex tool of this nature.

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%, and each parameter has a description in the schema. The tool description adds no additional parameter semantics beyond what the schema provides. Baseline 3 is appropriate because the description does not enhance understanding of parameters like algo or userName, but the schema already documents them.

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 it retrieves a list of mining earnings and specific data fields, but it doesn't explicitly distinguish itself from similar mining tools like BinanceMiningAccountEarning or BinanceHashRateResaleList. The verb 'Retrieves' and resource 'list of earnings' give clear purpose, but sibling differentiation is absent.

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 is provided on when to use this tool versus alternatives like BinanceMiningAccountEarning. The description does not mention prerequisites, required parameters (algo, userName), or scenarios where this tool is preferred. Without this context, an agent cannot make an informed choice among the many mining-related sibling tools.

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