BinanceHashRateResaleList

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what is returned, but does not mention pagination behavior (despite pageSize and pageIndex parameters), read-only nature, authentication requirements, or any rate limits. The field enumeration adds some context, but operational behavior beyond the basic return value is missing.

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, focused sentence that efficiently conveys the tool's purpose and key output fields. It contains no fluff or redundant phrasing, earning full marks for conciseness and structure.

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?

The tool is relatively simple with optional parameters and no output schema. The description covers the core purpose and return fields, which is adequate for a basic list operation. However, it lacks pagination details, usage positioning among sibling tools, and any mention of response structure or potential errors, so it is average in completeness.

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%, as pageSize, pageIndex, and recvWindow are each described in the schema. The tool description adds no additional parameter meaning beyond what the schema already provides, so it meets the baseline of 3.

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 returns a list of hashRate resale configurations and enumerates the specific transfer details included (algorithm, hashrate amount, sender/receiver usernames, dates, status). This distinguishes it from sibling tools like BinanceHashRateResaleDetail (single configuration) and BinanceCancelHashRateResaleConfiguration (cancellation).

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. It does not mention related tools such as BinanceHashRateResaleDetail for viewing a single configuration or BinanceHashRateResaleRequest for creating one, nor does it specify any prerequisites or exclusions.

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