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

Beyond the readOnly/idempotent annotations it discloses real behavioural context: the table's small size (tens of addresses), its provenance (public block-explorer labels, activity-checked on chain), the activity.checked field indicating whether a transfer read ran, and the clusterable flag constraint on how results may be restated. That is unusually rich disclosure of limits and result semantics.

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 core capability and the caveats are front-loaded and each paragraph carries real content, but the prose is dense and the instruction about repeating the clusterable flag is an odd meta-directive that could be tightened.

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?

With no output schema, the description carries the burden of explaining returns and does so: row contents, activity.checked, the clusterable flag, and hit/miss interpretation. It is nearly complete, though the full set of returned fields is not enumerated.

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?

There is only one parameter and schema coverage is 100%, so the schema already documents the accepted address formats. The description restates the same formats and adds nothing further (it even omits the schema's 'case is preserved' note), so the baseline of 3 applies.

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 verb and resource: whether an address is a labelled centralised-exchange wallet in Scienter's published table, plus clustered-address and exchange-activity reads. This is clearly distinguishable from siblings like ofac_check or wallet_score, which target different label sets.

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 gives strong interpretation guidance: a miss means no label is held, not that the address is unaffiliated, and a hit on an exchange hot/cold wallet means nothing about linkage between two funders. It does not explicitly route the agent to or away from named sibling tools, so it stops short of a 5.

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