fetchTokenPriceByAddress

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

The description indicates a read operation ('Get') but lacks any behavioral details such as rate limits, error handling for invalid addresses, or precision of prices. With no annotations, more disclosure would be beneficial.

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 a single concise sentence containing all essential information: action, resource, and input criteria. No unnecessary words.

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 simple one-parameter tool, the description adequately explains what it does and the required inputs. Although no output schema exists, the expected result (USD prices) is implied. Minor gap: no mention of multi-token support.

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 schema covers all parameters with descriptions and examples. The description adds no new semantic information beyond referencing 'contract address and network', which is already captured.

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 fetches current USD prices for tokens using contract address and network. It distinguishes from sibling tools like fetchTokenPriceBySymbol which uses symbols.

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 implies usage when contract address and network are known, but does not explicitly mention when to avoid or prefer alternatives (e.g., use fetchTokenPriceBySymbol for symbol-based queries).

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