getBizTokenPriceList

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

No annotations are provided, so the description carries full burden. It describes the tool as a batch query that returns market data with no indication of destructive behavior or side effects. It transparently states the input format and output fields, which is appropriate for a read-only data retrieval tool.

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 contains some redundancy: the 'Do NOT' instructions appear twice (once in a block, once in the agent hint). It could be more concise by removing duplication while keeping the key guidance.

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?

Despite no output schema, the description enumerates the returned fields (price, 24h change, volume, market cap, liquidity, holder count). It explains the input format, provides source recommendations, and gives negative usage guidelines. This is complete for a market data query tool.

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 single parameter 'tokenAddressInfo' is an array of objects with chainCode and tokenAddress. Schema description coverage is 0%, but the description advises to get these values from getBizTokenList or getAssetList, adding context beyond the schema. However, it does not elaborate on the structure of the array or individual fields.

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 it batch queries token prices and market data by chain code + token address pairs. It lists the specific data returned (price, 24h change, volume, market cap, liquidity, holder count) and distinguishes from siblings by explicitly stating what it should not be used for (token discovery vs. getBizTokenList, project info vs. getBizTokenDetails).

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 explicitly tells when to use (for token prices and market data given chainCode+tokenAddress pairs) and when not to use (not for discovery or project info). It provides clear alternatives (getBizTokenList for discovery, getBizTokenDetails for project info) and includes an agent hint summarizing usage.

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