BinanceAccountList

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

With no annotations provided, the description carries the full transparency burden. It clearly indicates a read operation ('Retrieve') and discloses the output structure (hourly/daily hashrate, timestamps, rejection rates). It does not mention pagination or data range, but for a read-only reporting tool this is adequate.

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 two sentences, front-loaded with the primary action and resource, followed by concise details about return data. No filler or redundant information.

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 no output schema, the description's explanation of return values is important, and it covers key elements (hourly/daily hashrate, timestamps, rejection rates). It is sufficiently complete for two required parameters and a clear scope, though mentioning time range boundaries or pagination would make it more complete.

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 already provides full descriptions for all three parameters (algo, userName, recvWindow), so the description adds no additional parameter-level meaning. The mention of 'mining account' reinforces userName but does not go beyond the schema.

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 retrieves hashrate statistics for a mining account, with a specific verb ('Retrieve') and resource. It also details the return content (hourly/daily data, timestamps, rejection rates), distinguishing it from sibling mining tools like earnings or resale lists.

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 implies this tool is for mining account performance monitoring, but it does not explicitly state when to use it over alternatives such as BinanceMiningAccountEarning or BinanceStatisticList. There are no exclusions or alternative tool suggestions, so usage guidance is only implied.

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