BinanceGetWbethWrapHistory

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

No annotations are provided, so the description carries the full burden for conveying behavioral traits. The verb 'retrieve' implies a read-only operation, and it mentions the returned content types, but it does not explicitly state read-only semantics, auth requirements, rate limits, or pagination behavior. It is adequate but not rich.

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, front-loaded sentence with no filler. It efficiently communicates the tool's core purpose and key output fields, earning its place without unnecessary verbosity.

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 has no output schema, so the description should helpfully explain the return shape. It mentions asset conversion details, exchange rates, and transaction status, but it omits pagination/response structure and does not clarify how the optional time filters affect the results. It is minimally complete but leaves gaps.

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 has 100% parameter coverage, with each parameter (size, current, endTime, startTime, recvWindow) already described. The tool description adds no parameter-level detail, but because the schema is comprehensive, the baseline of 3 is appropriate.

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 uses the specific verb 'retrieve' and clearly identifies the resource: 'historical records of WBETH wrap operations.' It also lists the key returned data (asset conversion details, exchange rates, transaction status), making it distinct from sibling tools like BinanceGetWbethUnwrapHistory, BinanceGetWbethRateHistory, and BinanceGetWbethRewardsHistory.

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?

There is no guidance on when to use this tool versus the many similar history tools among its siblings (e.g., wrap vs unwrap history, rate history, rewards history). The description only states what the tool does, not when it should be chosen or when an alternative would be more appropriate.

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