BinanceWalletDustTransfer

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

With no annotations, the description carries the full burden of disclosing behavior. It merely states the action without detailing side effects, irreversibility, permission requirements, or what the conversion entails (e.g., selling small balances). This lack of behavioral context makes it hard for an agent to anticipate the tool's 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, clear sentence that immediately conveys the tool's purpose. It is efficiently worded with no superfluous content, making it easy to parse and remember.

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?

Given the tool likely performs a real financial action (converting dust to BNB), the description lacks essential context such as what happens to the dust assets, whether the operation is irreversible, or what the response contains. Without an output schema or annotations, this minimal description is insufficient for an agent to fully understand the tool's behavior.

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?

Input schema coverage is 100%, with 'asset' described as 'Array of asset symbols to convert' and 'recvWindow' having a constraint. The description adds no extra meaning beyond the schema, meeting the baseline but not exceeding it.

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 'Convert dust assets to BNB' clearly states a specific action (convert) on a specific resource (dust assets) with a target (BNB). It distinguishes itself from sibling tools like BinanceWalletGetAssetsThatCanBeConvertedIntoBnb (which lists assets) and BinanceWalletDustlog (which shows logs).

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 no guidance on when to use this tool versus alternatives, such as checking which assets are convertible first or reviewing dust logs. It does not mention prerequisites or common use cases, leaving the agent to infer usage solely from the tool name.

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