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

Annotations provide readOnlyHint=true, and the description adds the crucial behavioral detail of how prices are derived (CoinGecko for loan tokens, market oracle × loan token price for collateral), and that these match the strategies' priceUsd fields. This goes beyond the annotation's safety hint.

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 brief and packs essential information into two sentences, front-loading the purpose and then explaining the pricing sources. No filler or redundant phrasing.

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 read-only tool with one parameter and an optional chainId, the description is complete. It explains the output content, data sources, and alignment with strategy prices, so the agent has all necessary context to call it 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?

The single parameter chainId is fully described in the schema with the supported values and default. The description does not add extra semantics beyond what the schema provides, but the schema coverage is 100%, so this is acceptable.

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 returns current USD prices for all loan and collateral tokens, mapping token address to USD, and mentions equity-vault stocks. It distinguishes itself from siblings by focusing on pricing data, unlike transaction builders and strategy listings.

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 when to use it (to retrieve current prices) and notes the inclusion of equity-vault stocks, but does not explicitly state when not to use it or name alternative tools. Since it's a data retrieval tool standing apart from transaction builders, the context is clear enough.

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