What each DEX venue contributes chain-wide

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

With no annotations to rely on, the description carries the full burden and does so exceptionally well. It discloses row-per-venue behavior including venues with no pools yet, the meaning of readingHistory/scan position, the floor semantics of counts, the Pons launchpad mapping onto Uniswap v3, and precise definitions for depthUsd, checkedAt, and headAt.

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 description is dense but justified: nearly every clause adds needed semantic detail about fields, timing, and edge cases. It is front-loaded with the purpose and trigger conditions, though the long middle sentence could be broken up for easier scanning.

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?

Given that there is no output schema and no annotations, the description provides a remarkably complete picture of the tool's return content and interpretation. It covers row identity, field definitions, date windows, edge cases for unread venues, and special launchpad behavior, leaving no major ambiguity for an agent deciding to call it or interpret its results.

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 input schema has zero parameters, so there is nothing for the description to clarify. The behavior of an unparameterized tool is fully explained, and the description focuses on the output semantics rather than inputs.

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 clearly identifies the tool's purpose: enumerating DEX venues on a chain and summarizing their aggregate value and pool/volume metrics. It even gives trigger scenarios ('ask before saying where a Stock Token trades', 'pool count looks implausibly low'), but it does not explicitly name or contrast sibling tools such as pools or activity.

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 description state when to use this tool: before claiming where a Stock Token trades, and when a venue's pool count looks suspicious. That is strong context, but it does not provide explicit exclusions or name alternative tools to use instead, so it falls just short of full guidance.

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