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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely useful context beyond them: it flags which fields (names, symbols, tags, method names) are attacker-controllable and wrapped as untrusted, which is real behavioral guidance for an agent. It still omits rate limits and behavior for unknown addresses.

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 opens with a clear framing sentence and then packs the return fields into one dense enumeration followed by a security caveat. It is information-dense and front-loaded, with no filler; the long single clause listing fields is slightly taxing but every element is functional.

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 explaining return values, and it does so comprehensively field-by-field, plus the untrusted-data caveat. It is nearly complete; only edge-case behavior (unknown address, partial data) is left unspecified.

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?

Only one parameter exists and schema coverage is 100% ('0x-prefixed 20-byte address'), so the schema fully documents it. The description adds no format, casing, checksum, or validation detail beyond the schema, making the baseline 3 the correct score.

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 (an address) and enumerates precisely what the tool returns — balance, contract/verification status, tags, scam flag, proxy info, creator, token metadata, and counters. That makes the tool's purpose unambiguous. It does not explicitly contrast itself with focused siblings like explorer_contract, explorer_token, or get_balance, 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 only implied: by listing a broad superset of address facts, it signals 'use me for a general address overview.' There is no explicit when-to-use guidance, no statement of when a narrower sibling (explorer_token, explorer_contract) is preferred, and no prerequisites or failure conditions.

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