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

No annotations are supplied, so the description carries the full disclosure burden, and it delivers very little: it never states that this is a read-only operation, whether results are cached, whether there are rate limits, or what happens when the optional baseChain is omitted. 'Get' weakly implies a safe read, but nothing confirms it.

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, no filler, with the core operation front-loaded before the use case. The second sentence is slightly generic but still earns its place by signaling intent.

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?

There is no output schema and no annotations, so the description is the only guidance available, yet it omits the most consequential behavioral question: how the optional baseChain alters the returned pairwise set (all-pairs versus anchored pairs). For a 3-parameter analytical tool this is a meaningful gap, though the core purpose is adequately conveyed.

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 100%, so the schema already defines symbol, provider, and the baseChain enum, making 3 the correct baseline. The description restates the required provider/symbol pair but adds no meaning for baseChain, which materially changes the computation ('Base chain for spread calculation').

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 a specific verb and resource ('Get pairwise price spreads across chains') scoped to a provider and symbol, which is concrete and unambiguous. It does not, however, explicitly distinguish itself from potentially adjacent siblings such as compare_oracle_deviation or get_correlation, so an agent must infer the boundary.

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?

'Useful for cross-chain arbitrage and risk tracking' hints at the intended context but gives no explicit when-to-use or when-not-to-use rule, and never names an alternative tool. Usage is implied rather than prescribed.

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