getAssetDetail

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

Describes the response structure (assetList array with 0 or 1 element) and explains the meaning of an empty array (user does not hold or token not available). It does not explicitly state the tool is non-destructive, but the description implies it is a read query. With no annotations, this is reasonably transparent.

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 front-loaded with the main purpose and key details. However, there is some redundancy between the description and the agent hint section (e.g., repeating the assetList structure and do-not-use instructions). Could be slightly more concise.

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 output schema, the description fully explains the return structure (assetList array, fields returned), the empty case meaning, and points to sibling tools for other needs. It covers all necessary context for an agent to invoke this tool correctly.

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% (no parameter descriptions in schema). The description tells the agent to get chainCode and tokenAddress from getAssetList or getBizTokenList, which adds context, but does not independently define the parameters' meaning or format. This is helpful but insufficient for full semantic clarity.

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 action: 'Query detailed holding information for a specific token by chain code and token address.' It lists specific return fields (quantity, USD value, unrealized PnL, etc.) and explicitly distinguishes it from sibling tools like getBizTokenPriceList and 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?

Provides explicit when-to-use (agent hint: when user asks about a particular asset), when-not-to-use (do not use for general market data or project info), and alternative tools (getBizTokenPriceList, getBizTokenDetails). Also advises where to obtain the required parameters (getAssetList or getBizTokenList).

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