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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description mentions returning price, source, and confidence, which overlaps with the output schema's job. It does not disclose rate limits, freshness/staleness, or what 'verified' guarantees beyond an annotation-level claim.

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?

A single dense sentence with no waste, and the core purpose is front-loaded. It is appropriately sized for a two-parameter read tool.

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 full annotations and a full output schema, so the description needn't explain returns or safety. However, given a rich sibling set including token.price and oracle.chain_status, the description should clarify how it differs and when to prefer it, which it fails to do.

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 both the chain enum and token format are already fully documented in the schema. The description adds no syntax or format detail beyond what the schema provides, which is the expected baseline when the schema does the heavy lifting.

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 states the resource (token price feed) and labels it a 'Data Oracle' with verified prices, which is clear enough as a purpose. However, it does not differentiate from the obvious sibling token.price, nor does it explain what 'Chain Proof signature' adds. The purpose is understandable but sibling differentiation is absent.

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 positions it as a 'lightweight alternative to Chainlink', which implies a comparison, but gives no when-to-use guidance relative to the sibling token.price or oracle.chain_status. There are no explicit conditions or exclusions for selecting this tool.

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