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

Goes well beyond the annotations: it discloses cost ($0.001 USDC per call), notes that an explicit list of unchecked items is returned, clarifies the evidence is static-only (no simulated sell, no safety certification), and even documents byte-parity with a REST endpoint. This is the behavioral context an agent needs before invoking a paid, open-world read.

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 opening sentence is front-loaded with the verdict payload, followed by the bytecode evidence and proxy check. It is dense but every clause earns its place; the pricing, static-evidence caveat, and endpoint-parity sentence are all load-bearing for a paid tool, though the description is on the longer side.

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?

For an aggregating verdict tool with a declared output schema, the description covers inputs, cost, evidence scope, and explicit non-claims. The remaining gap is only that it does not name which sibling primitives an agent could call instead for narrower reads, but the output schema carries return-value detail.

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 chain and token are already documented in the schema, and the description adds no syntax or format details for them. The embedded example URL does hint at the expected token format (0x-prefixed address) and default chain (base), but this is implicit rather than explicit param guidance.

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 ('assembled into a verdict' for a Base token) and enumerates exactly what evidence is bundled: deepest DEX pool metrics, bytecode-declared capabilities, and proxy status. It is clearly distinguishable from sibling primitives like chain_bytecode_capabilities, chain_proxy_check, and market_dex_pair_detail, which each cover only a slice of this aggregated verdict.

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 sets clear scope boundaries: 'Static on-chain and venue evidence only — never a simulated sell and never a certification of safety,' which tells the agent when this tool is appropriate versus a price/simulation tool. It stops short of naming explicit alternatives, but the negative constraints are unusually strong guidance.

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