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

With no annotations, the description carries the full burden and does provide meaningful behavioral context: it is a block-pinned snapshot, the response distinguishes enabled unsigned-calldata lanes from read-only venues, and it explains the review condition for read-only status. It does not detail permissions, failure modes, or response structure, but covers the key behavioral distinction.

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 core purpose. The venue list is long but necessary for clarity; the second sentence adds useful behavioral distinction. Minor redundancy from listing venues also present in the enum, but overall efficient.

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 a simple read-only lookup with one optional parameter and no output schema, the description explains what evidence is returned and the enabled/read-only distinction. It does not specify the shape of the evidence payload, but it is complete enough for an agent to call the tool correctly.

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 'venues' parameter is fully documented in the schema. The tool description lists the same venues in prose but adds no syntax, format, or selection semantics beyond what the schema already provides, so it meets the baseline of 3.

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 ('Get') and resource ('block-pinned code-identity evidence') scoped to reviewed Base DEX deployments, listing the covered venues. It is clearly distinct from market-data siblings like get_base_dex_market, but it never names or contrasts with those alternatives, leaving differentiation to inference.

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?

Usage is implied by the tool's nature—use it to inspect code-identity evidence for reviewed Base venues—but there is no explicit when-to-use, when-not-to-use, or alternative selection guidance relative to the many other Base DEX and market tools.

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