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

With no annotations provided, the description fully carries the behavioral burden. It discloses that the tool is free, that rewards are paid by the opener (not Tereno), that the reward is not escrowed, and that challenging is free at the claim's challengeEndpoint. This is rich, honest behavioral context that goes far beyond a simple read/list operation.

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 three short sentences, each carrying distinct information: cost, scope, and challenge mechanics. It front-loads the 'Free' fact and stays fully on-topic with no filler.

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 list tool with no output schema, the description thoroughly covers what claims are, how they are falsified, deadlines, reward source, and the challenge endpoint. This is complete enough for an agent to understand the tool's purpose and constraints without additional documentation.

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 single parameter 'limit' is fully described in the schema (100% coverage), so the description does not need to add parameter details. It contributes nothing beyond the schema, which meets the baseline for high schema coverage.

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 uses a specific verb ('Lists') and a clear resource ('open, deterministic claims about Base proxy contracts'), with additional context about rewards and falsification. This clearly differentiates it from sibling tools like tereno_publish or tereno_catalog.

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 implies when to use the tool (to find claims you could challenge) and provides context (free, open), but it does not explicitly state when not to use it or name alternative tools. Since no exclusions or alternatives are given, it earns a mid-range score.

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