SmallAssetQuote

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

With no annotations, the description fully discloses behavioral traits: permission requirements, rate limiting, wallet restrictions, transaction limits, unsupported account types, potential under-execution of amounts, and load balancing strategy. This exceeds expectations for transparency.

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 compact and well-structured: a clear opening sentence followed by six bullet points, each adding distinct information without redundancy. Every sentence earns its place.

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 lack of output schema and annotations, the description covers the main purpose and constraints but falls short on parameter semantics and detailed return structure. It explains return values minimally ('quote ID and per-coin conversion details') and leaves out parameter validation contexts.

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 0%, so the description should clarify parameters. It implicitly relates accountType to Unified wallet and fromCoinList to a list of up to 20 coins, but does not explain valid values for accountType or toCoin, nor the exact syntax for fromCoinList. This leaves significant ambiguity for an agent.

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: 'Apply for batch conversion quote for a small asset list.' It specifies that it returns a quote ID and per-coin conversion details, distinguishing it from sibling tools like SmallAssetConvert, which presumably executes the conversion.

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 explicit constraints: API key permission (Convert), rate limit (5/s), wallet support (Unified wallet only, eb_convert_uta), max coins per transaction (20), unsupported custody accounts, and balance behavior. While it doesn't explicitly say 'use this before SmallAssetConvert', the context implies it. It lacks explicit 'when not to use' but the constraints serve as guidance.

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