BinanceGetC2CTradeHistory

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

With no annotations, the description carries the full transparency burden. It discloses that the operation is a read-only retrieval and lists the types of details returned, but it does not mention pagination behavior, authentication requirements, or potential rate limits, which are relevant for a history endpoint.

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, well-structured sentence that efficiently communicates the tool's purpose and the major fields involved, with no wasted words or unnecessary repetition.

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 description adequately covers the scope ('own past C2C trades'), the type of data returned (asset type, direction, fiat, status), and implicitly the historical nature. Given that the schema fully documents all parameters, this is sufficient for a simple read-only tool, though it could mention pagination or time constraints.

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 descriptions for all four parameters, so the description does not add significant new parameter-level semantics. It only gives a general overview of the data returned, meeting the baseline for high schema coverage.

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's function with a specific verb ('retrieve') and resource ('own past C2C trades'), and distinguishes it from sibling tools like BinanceGetPayTradeHistory or BinanceGetFiatPaymentsHistory by specifying C2C trades.

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 provides clear context that this tool is for retrieving the user's own C2C trade history, which implies when to use it. However, it does not explicitly mention alternatives or exclusions, so it falls short of a 5.

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