list_price_feeds

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

No annotations exist, so the description carries full burden. It discloses that the tool reads on-chain descriptions and deduplicates, clearly indicating a read-only operation. However, it does not mention rate limits, performance, or potential side effects.

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, well-structured sentence that front-loads the purpose ('Discover Chainlink price feeds') and adds key details about the method and deduplication. No wasted 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?

No output schema, so the description should explain return values. It does not mention what is returned (e.g., addresses, aggregator details, or deduplication results). Given moderate complexity and lack of output schema, the description is incomplete.

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 50% (query has a description). The tool description does not explain the limit or query parameters beyond the schema defaults. The agent might not understand how 'query' relates to 'reading each candidate's description()'—likely an explorer search term, but not clarified.

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 discovers Chainlink price feeds by reading descriptions and deduplicates proxies. It uses specific verbs and distinguishes itself from sibling tools like price_feed_registry or read_price_feed.

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 for discovering available price feeds but provides no explicit guidance on when to use it versus alternatives like price_feed_registry or when not to use it. No exclusions or context provided.

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