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

Beyond the readOnly/idempotent/openWorld annotations, it discloses auth posture (no auth), a shared rate limit (1200 req/min across all tools), latency behavior ('never waits for a slot'), and a state edge case (updated_at null until first ingest). It also flags data provenance and a caution to verify against the official SDN list.

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?

Front-loaded with the returned payload before use cases and exclusions, and nearly every sentence carries routing or behavioral information. The closing verification/legal disclaimer is defensible for sanctions data but adds length without helping invocation.

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 full burden of describing the return payload (per-chain counts, total, updated_at semantics, source), and it does so. Combined with the no-auth/rate-limit notes, an agent has everything needed to call and interpret this tool.

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?

Zero parameters, so the baseline is 4. The description confirms the no-argument design and that one answer covers every chain, which is a useful signal, but there is no additional parameter meaning to convey.

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+resource: it reports the OFAC SDN list coverage as the scanner holds it, enumerating the exact fields returned (evm_count, solana_count, tron_count, total, updated_at, source). It explicitly separates itself from get_address_compliance and get_address_risk, so an agent can distinguish it from siblings without opening a schema.

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?

Gives positive triggers ('date the sanctions input behind a verdict', 'tell a clear OFAC flag from an unloaded list') and explicit negative routing to three named alternatives (get_address_compliance, get_address_risk, get_sync_status) with the condition that selects each.

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