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

With no annotations, the description must carry the full behavioral burden, and it does disclose meaningful traits: the snapshot is 'fresh, block-pinned', the scope is one reviewed pair, and the quote ladder is 'bounded'. However it never states that the call is a read-only/no-side-effect operation, how block-pinning is enforced or how stale it can be, what 'bounded' means for the ladder, or anything about latency/rate limits. Useful context, but incomplete for a zero-annotation tool.

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 verb+resource, followed immediately by the scope disambiguation. Every clause earns its place: the field inventory tells the agent what comes back, and the negation clause prevents mis-selection.

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, yet the description enumerates the returned evidence, which is exactly what the agent needs to judge suitability. For a one-parameter, single-pair market read, the remaining gap is mainly the absence of an explicit read-only/freshness statement, which is borderline given the 'block-pinned' wording.

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 optional parameter is fully described in the schema (enum of the one reviewed pair id, with a default), so the schema does the work and the description adds nothing about it. Baseline 3 applies.

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?

States a specific verb ('Get'), resource ('Base QuickSwap V2 USDC/USDT market evidence'), and enumerates the payload (factory/router/pair identities, reserves, spot, quote ladder). It also draws explicit boundaries against siblings: 'not an oracle-consensus price' (cf. get_consensus_price) and 'not a generic QuickSwap route' (cf. route/swap tools), so an agent can select it between near-neighbors without reading either schema.

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 negative framing ('This is one reviewed pair, not an oracle-consensus price or a generic QuickSwap route') gives an agent a clear condition for when to pick this tool and when to reach for consensus or route tools instead. It stops short of prescribing positive usage conditions or naming the alternatives by tool name, so it is strong but not fully explicit.

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