BinanceGetConvertTradeHistory

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

No annotations are provided, so the description must convey behavioral traits. It does disclose read-only behavior ('retrieves') and pagination support (limit up to 1000). However, it does not mention authentication prerequisites, potential rate limits, or what fields are returned, leaving a moderate transparency gap.

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. It front-loads the core purpose and then adds the key pagination detail. There is zero fluff, every word earns its place.

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 (4 params, no output schema), so the description covers the basics: what it does, time range, and pagination. However, since there is no output schema, it would be more complete to hint at the structure of the returned trade history (e.g., a list of trade objects). The description is adequate but not fully self-sufficient.

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 descriptions cover 100% of parameters, so the baseline is 3. The description adds little beyond the schema: it mentions the limit parameter's max (already in schema) and the time range (already described via startTime/endTime). It does not clarify parameter types, units, or relationships beyond what the schema provides.

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 verb ('retrieves') and the specific resource ('token conversion trade history'), and it distinguishes this tool from sibling trade history tools like BinanceGetC2CTradeHistory by explicitly naming 'token conversion'. It also specifies the time range scope, making the purpose unambiguous.

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 gives clear context: it is for retrieving the user's token conversion trade history within a specified time range. It does not explicitly exclude alternatives or mention when not to use it, but the unique resource type makes the intended use clear. However, with many sibling tools, a brief note on when to prefer this over similar trade history tools would have been better, so it misses a 5.

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