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

With no annotations, the description carries the full behavioral burden and does substantial work: it discloses a rate limit (3 calls/hour/IP), that the quota is shared with the website, the paid tier price ($0.060/call) and the x402 payment mechanism at /v1/known. It also characterizes output content as 'facts and flags only, never advice.' It does not mention auth details beyond x402 or pagination/response behavior, keeping it off a 5.

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?

Three sentences, each with a distinct job: purpose/content scope, nature of the output, and access terms. The first sentence is dense and slightly awkward (the colon list interrupts the main clause), but nothing is redundant and the access constraints are placed last where they belong.

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?

There is no output schema and no annotations, so the description must carry the return-behavior burden. 'Do we hold a research note' reads like an availability question while 'Facts and flags only' implies substantive content is returned, leaving the actual response shape ambiguous. Pricing, rate limits and input domain are covered, but the return semantics gap holds this to a 3.

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%, so the single parameter q (asset symbol, protocol name, chain name or contract address) is already fully documented. The description restates roughly the same list and adds 'role' as an accepted input type, which is a small semantic extension not present in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 resource (held research notes) and enumerates concrete content types it covers: dead redemption bridges, ticker collisions, ended points programmes, closed marketplaces, capital gates. It distinguishes itself from data-oriented siblings by scoping to signals 'no price feed or TVL number will tell you.' It never names a sibling explicitly (safety, stable, chain could plausibly overlap), so it stops short of 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?

Usage is implied rather than stated: an agent can infer this is for qualitative/flag-level facts about an asset, protocol, chain or role. There is no explicit when-to-use/when-not, no named alternative among siblings, and no guidance on how this differs from safety or stable lookups. The implied context is clear enough for a 3, but nothing routes the agent decisively.

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