getBizTokenPriceList

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

Annotations already mark it readOnlyHint and openWorldHint, and the description adds useful behavioral detail: it returns a defined set of market metrics and handles batch pairs. There is no destructive or state-changing behavior left undisclosed.

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 first sentences are clear and well front-loaded, but the 'Agent hint' section repeats the same guidance almost verbatim, adding no new information and wasting tokens.

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?

For a read-only batched price tool with no output schema, the description adequately covers return fields, input sourcing, and clear exclusions, leaving no major ambiguity about how or when to call it.

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?

Although the schema has no property descriptions, the description compensates by explaining that the parameter is a chainCode + tokenAddress pair, that multiple pairs are accepted, and that the values should be sourced from getBizTokenList or getAssetList.

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 identifies the tool as a batch market-data query endpoint keyed on chainCode + tokenAddress pairs, and explicitly contrasts it with getBizTokenList (discovery) and getBizTokenDetails (project info), so an agent can select it appropriately.

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?

It explicitly states when to use the tool (for prices, 24h change, volume, market cap, etc.), where to source the inputs (getBizTokenList or getAssetList), and explicitly says when NOT to use it, naming the alternatives.

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