QuerySmallAssetList

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

Without annotations, the description discloses important behavioral traits: API key permission needed, rate limit of 10/s, Unified wallet requirement, and conversion range. It does not cover error behavior or result formatting, but covers key operational details.

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 very concise, using a single sentence for main purpose followed by bullet points for constraints. Every sentence adds value with no 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?

The description covers purpose and constraints adequately for a simple query tool, but lacks details on return value structure. Since there is no output schema, the agent may not know what fields are returned, making it somewhat incomplete.

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 has 0% description coverage and no descriptions for parameters. The tool description indirectly hints at the purpose of parameters (e.g., accountType likely refers to wallet type) but does not explicitly explain them, leaving the agent dependent on naming conventions.

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 the tool's purpose: querying small-balance coins eligible for dust conversion and supported to-coins. It provides specific resource details and additional constraints like permission and wallet type, distinguishing it from generic query tools.

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 includes usage constraints such as required API permission, rate limit, and wallet type, but does not explicitly mention when to use this tool versus alternatives like SmallAssetConvert or QuerySmallAssetConvertOrder.

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