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

With no annotations, the description carries the full burden and does add real behavioral context: it defines what a row contains, explains the eitherExecutable flag, and explicitly scopes the coverage caveat that hooked v4 pools are not scanned. That negative-space disclosure is valuable. It stops short of describing freshness, refresh cadence, or result format.

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?

Four short sentences, front-loaded with what the tool is before the interpretive caveats. Minor telegraphic/inconsistent phrasing ('each row reports', lowercase mid-sentence) but no filler that could be cut without losing a constraint.

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 zero-parameter read tool with no output schema, the description conveys what the rows mean and how to interpret the boolean against stocktoken_quote, which is the main thing an agent needs. Exact column layout and data freshness remain unstated but are not blocking.

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 tool takes zero parameters, so the baseline is 4; there is no parameter syntax to explain and the description spends its words on row semantics instead, which is the right allocation.

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 resource and scope: a liquidity matrix for major USDG pairs on chain 4663, with rows covering hookless v4 and on-chain v3. This is concrete enough to distinguish it from stocktoken_quote or stocktoken_find_pools, though it never names those siblings explicitly.

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 provides one conditional rule of use ('If stocktoken_quote.executable is false, do not promise a fill'), which is genuine guidance, but it never states when to reach for this tool versus stocktoken_find_pools or stocktoken_quote. Usage is implied by context rather than spelled out.

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