BinanceGetWbethUnwrapHistory

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

Since no annotations are provided, the description carries the transparency burden. It discloses the types of data returned (asset conversion details, exchange rates, transaction status), which adds value. However, it does not cover pagination behavior, response structure, or any prerequisites or side effects. For a read-only 'Get' tool this is acceptable but leaves gaps.

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 conveys the tool's purpose and key output details. It is efficient, though it could be slightly more concise by omitting unnecessary phrases like 'API allows users to'.

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?

For a straightforward paginated history tool with no required parameters, the description is adequate but not rich. It doesn't explain default behavior, how the unwrap history relates to wrap or rewards history, or whether there are any limitations. The presence of an output schema could have helped but is absent.

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%, with each parameter already described (size, current, startTime, endTime, recvWindow). The tool description does not add any additional parameter-specific context beyond the schema, so 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 clearly states a specific verb ('retrieve') and resource ('historical records of WBETH unwrap operations'), and identifies the key output fields (asset conversion details, exchange rates, transaction status). It effectively distinguishes this from sibling tools like BinanceGetWbethWrapHistory, BinanceGetWbethRewardsHistory, and BinanceGetEthRedemptionHistory by explicitly naming 'Unwrap History'.

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 retrieving WBETH unwrap history, but it doesn't provide explicit when-to-use guidance or mention any alternatives. Sibling tools (e.g., BinanceGetWbethWrapHistory) are not referenced, so the agent must infer from the name and description alone.

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