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

With no annotations, the description carries the full burden. It usefully discloses that an assay is a reverted real buy-and-sell, the emitting contract address, and the event payload (verdict, round-trip cost, streak), but it never states this tool's own read-only safety profile, permissions, or pagination/return shape.

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 first two sentences are dense and front-loaded with the definition, but the third sentence pivots to how to *create* an assay via a direct contract call, which is tangential to a read tool and adds routing noise rather than value for invoking this tool.

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?

No output schema and no annotations exist, so the description should fully cover return behavior and safety. It explains the assay's conceptual outputs but does not describe what this read tool actually returns or how results are shaped, leaving a gap for an agent to close on its own.

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 there is only one optional param, so the baseline is 3. The description adds genuine meaning beyond the schema: omitting 'token' returns every pool's last assay, while supplying it scopes to one token's assay.

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 gives a specific verb+resource (read every pool's last assay and streak, or one token's) and defines what an assay is, so an agent understands the purpose without opening the schema. It does not, however, explicitly differentiate this from nearby siblings such as arc_verdict or arc_trust_check, which is what would be needed for a 5.

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 implies usage by stating the two modes ('read every pool's last assay' vs 'one token's'), but never says when to choose this over alternatives like arc_verdict or arc_contract_read. The 'to make one' sentence describes a contract call rather than routing guidance for this tool.

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