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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: values are block-pinned, and the Factory, QuoterV2, and Pool runtime identities are re-verified at the quoted block. It stops short of stating read-only semantics explicitly, latency/RPC cost, or failure behavior for an unverified pool.

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?

Three short sentences, zero redundancy, and the core purpose plus the block-pinning guarantee are front-loaded. The negative scoping sentence earns its place by preventing confusion with oracle price tools.

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, so the description should convey what 'market evidence' actually returns (quote amounts, tick/liquidity, gas estimate, verification status). It pins the trust model well but leaves the payload shape ambiguous, which is the main gap for a single-param read tool.

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% and the single profileId enum already documents the only valid pool id with its default, so the schema does the heavy lifting. The description reinforces the 'allowlisted'/'one pool' constraint but adds no format or selection detail beyond what the enum and its description provide.

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 and resource ('Get fresh, block-pinned market evidence') scoped to exactly one allowlisted PancakeSwap V3 Base pool. It also draws an explicit boundary against the oracle-price siblings ('not an oracle-consensus price'), so an agent can separate it from get_consensus_price and get_base_dex_market 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?

The clause 'This is DEX venue context, not an oracle-consensus price' implicitly routes the agent away from oracle tools, which is a real usage signal. However, it never states the positive condition for choosing this over get_base_dex_market, get_aerodrome_slipstream_market, or prepare_pancakeswap_v3_swap, and gives no explicit when-not guidance.

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