BinanceWrapBeth

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

With no annotations, the description must disclose side effects, but it only states the action and return values. It does not mention that this is a transaction that will debit BETH from the account, require a BETH balance, or have any fees/prerequisites. The word 'convert' implies a write but lacks explicit disclosure of behavioral impact.

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 concise sentence that front-loads the purpose ('Wrap BETH API') and includes the key output details. No redundant words or filler, making it easy to parse.

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 a simple conversion operation with no output schema, and the description does mention the response includes the wrapped amount and exchange rate. However, it omits important context like prerequisites (BETH balance), potential fees, or how the exchange rate is set. Given the lack of annotations, this leaves some gaps for a financial operation.

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 coverage is 100%, with 'amount' and 'recvWindow' already described. The description adds no additional parameter-level meaning beyond reiterating the conversion context. Since the schema handles parameter documentation, a baseline score 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 'convert BETH into WBETH' with a specific verb and resource, and mentions the result (wrapped WBETH amount and exchange rate). It distinguishes from sibling tools like BinanceGetWbethWrapHistory and BinanceRedeemEth, which handle history and unwrapping respectively.

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: this tool is for wrapping BETH into WBETH. It implies when to use it, but does not explicitly mention alternatives or exclusions. The sibling names are self-explanatory, reducing the need for explicit exclusion notes.

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