getChainlinkPrice

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

With no annotations, the description carries the full burden. It discloses the staleness flag based on a 1-hour threshold, which is helpful. However, it does not mention return format, error behavior for unsupported chains/pairs, or whether the operation is read-only, leaving notable gaps.

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?

Two sentences, front-loaded with the primary action, and no filler. Every phrase earns its place, including the staleness behavior.

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?

The tool has no output schema, so the description should clarify return values. It only mentions staleness flagging, not the price payload or units. Also, a brief pointer to getChainlinkRoundPrice for historical rounds would improve completeness, but for a simple two-param fetch, it is minimally adequate.

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 description coverage is 100%, so the schema already documents both parameters. The description adds an example (ETH/USD on ethereum) but no extra constraints or format details. The baseline 3 is appropriate because the description does not compensate beyond what schema provides.

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 the latest on-chain Chainlink price for a pair on a supported chain, with a concrete example. It is differentiated from Pyth tools by name, but not explicitly distinguished from the sibling getChainlinkRoundPrice, so it loses full marks.

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 getting the latest price, but provides no explicit guidance on when to use this over getChainlinkRoundPrice or listChainlinkFeeds. It also does not mention any prerequisites or exclusions, leaving the context partially implied.

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