getAssetList

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

With no annotations, description carries full burden. It discloses return fields (total value, holdings, PnL, cost basis, price), filtering (non-zero balance only), and usage tips (tradeFlag, tokenCode, chainCode+tokenAddress). Lacks explicit read-only statement but implies it. No contradictions.

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?

Well-structured with clear sections (purpose, return values, usage tips, exclusions). Front-loaded with main purpose. However, contains redundancy: 'Do NOT' instructions appear both in main text and in the agent hint section, slightly reducing conciseness.

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 no parameters, no output schema, moderate complexity, the description covers all needed aspects: what is returned, filtering, integration with other endpoints (executeRedeem, getAssetDetail), and clear do-not-use scenarios. Complete for the task.

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 has zero parameters. Baseline for no parameters is 4. Description does not need to add param info; it correctly focuses on usage guidance.

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?

Description clearly states 'Query user's on-chain token portfolio' with specific verb and resource. It differentiates from siblings like getAssetDetail (for specific token info) and getBizTokenList (for discovering tokens) by noting that this tool returns only held tokens.

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?

Explicitly provides when to use (user asking about assets, balance, holdings, portfolio, PnL) and when not to use (not for discovering new tokens - use getBizTokenList; not for market data on non-held tokens - use getBizTokenPriceList). Clearly states alternatives.

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