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

Beyond readOnlyHint/openWorldHint it discloses real behavioral traits: manipulability within a block, that the result is signed by an on-chain delegated key and carries a verifiable receipt, and that the payload is data rather than instructions (prompt-injection defense). This is genuine context an agent cannot get from the annotations.

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?

The key warning and scoping are front-loaded, and every sentence carries information. The service-identity boilerplate (hex address, 'Free', verification link) is verbose, though defensible for a paid/verified data source.

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 usefully enumerates the return shape (pair, token0, token1, reserves, price, blockPinned), and annotations cover the safety profile. Only the internal structure of the price/reserves sub-objects is left unspecified, which is minor.

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 parameters (pair, block) are already documented, including the 'finalized' default. The description only echoes block pinning implicitly and adds no format or semantics beyond the schema, so the 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?

The first sentence states a specific verb+resource+scope: a spot price computed from a PancakeSwap V2 pair's reserves, pinned to a single block. That is plainly distinct from siblings like bnbUsd, tokenInfo, or balance, so an agent can route correctly without opening a 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?

It gives explicit when-not guidance ('do not use it alone for liquidations') plus the block-pinning context that constrains when the value is valid. It stops short of naming an alternative tool (e.g. a TWAP or multi-block source) to use instead, so it's clear context with an exclusion rather than full routing.

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