BinanceWalletAssetDetail

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

No annotations are provided, so the description carries the full burden. It only says 'Get asset details,' which implies a read operation but does not disclose what is returned, whether it requires authentication, or any other behavioral traits. This is no more informative than the tool name itself.

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 short phrase, but it is under-specified rather than concise. It restates the tool name and does not earn its place by adding useful information. Proper conciseness should front-load meaningful content, which is absent here.

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 only 2 parameters, but no output schema and no annotations. The description should at least clarify what 'asset details' means, but it does not. Given the complexity and the presence of many sibling tools, the description is inadequate for selecting and invoking the tool correctly.

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% description coverage for both parameters: 'asset' is described as 'Asset symbol' and 'recvWindow' with its constraint 'The value cannot be greater than 60000'. Since the schema provides full parameter meaning, the description does not need to add more, and the baseline of 3 applies.

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 'Get asset details' is essentially a tautology of the tool name BinanceWalletAssetDetail. It does not specify what kind of details, which asset, or how it differs from sibling tools like BinanceWalletUserAsset or BinanceWalletFundingWallet.

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. There is no mention of prerequisites, use cases, or exclusions. With many wallet-related sibling tools, the lack of usage context leaves the agent without direction.

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