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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description's 'never creates an order or signs a transaction' largely restates that, adding only the informational scope of what is being read; no new behavioral traits (auth, rate limits, failure modes) are disclosed.

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 tight sentences with the content list front-loaded and the key non-mutation disclaimer second. Efficient and free of filler, though the first sentence is a dense comma-run list.

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?

With no output schema, the description's enumeration of returned content effectively stands in for a return-value description, and the mutation disclaimer covers the main risk concern. The gap is the unaddressed 'network' parameter, which leaves the agent without guidance on how input affects output.

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 'network' parameter has 0% schema description coverage, and the description never mentions it. The enum supplies the allowed values (base/polygon/solana), but its meaning and effect—e.g., whether it scopes the returned chains—are undocumented in both description and schema.

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 names a specific verb (Read) and enumerates the resource contents (supported chains, USDC contracts, gas assets, price rules, owner-approval guidance), so the agent knows exactly what information this returns. It also contrasts itself against write-oriented siblings by noting it never creates an order or signs a transaction, though it doesn't name those siblings directly.

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?

There is no explicit when-to-use statement or named alternative. The clause 'This never creates an order or signs a transaction' implicitly positions it as the informational precursor to create_quote/submit_payment_proof, which is implied guidance rather than explicit routing.

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