QuerySmallAssetList

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

The annotations already mark the tool as read-only, and the description adds useful operational behavior beyond them: API key permission Convert, 10/s rate limit, Unified-wallet-only support, and the conversion amount range. This helps an agent understand constraints that annotations and schema do not convey.

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 compact five-line list with no filler. The main purpose is front-loaded, and each bullet adds a distinct operational fact without redundancy.

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 simple two-parameter read endpoint, most constraints are covered, but the optional fromCoin behavior is undocumented and there is no output schema to define the response shape. An agent can likely call it correctly with accountType=eb_convert_uta but may guess about fromCoin usage.

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 0%, so the description carries the burden. It partially compensates by hinting at accountType via 'Only supports Unified wallet (eb_convert_uta)' and by framing the query context as account balances. However, it never explains the optional fromCoin parameter or clarifies possible accountType values beyond that hint.

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 begins with a specific verb and resource: it queries small-balance coins eligible for dust conversion plus supported to-coins. This clearly distinguishes it from execution or quote endpoints like SmallAssetConvert and SmallAssetQuote.

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?

It provides clear context: this is the pre-conversion eligibility query for an account, requiring Convert permission and Unified wallet support. It does not explicitly contrast it with related endpoints like QuerySmallAssetConvertOrder or SmallAssetQuote, but the intended role is strongly implied.

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