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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint, so the closing 'Behavior: read-only' sentence is largely redundant. The genuinely additive traits are 'Free' and the openWorld framing (results come from third-party registries and may be empty or stale), but nothing is said about latency or what a miss looks like.

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 and short, which is good, but the leading one-liner and the 'Use when you want to cross-reference a wallet against the open ERC-8004 identity and reputation registries' sentence restate the same content almost verbatim, and the trailing 'Behavior: read-only' repeats the annotations. Roughly a third of the text is redundant.

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 is the only place to learn what comes back (an identity record? a reputation score? an empty result when the registry has no entry for the wallet?). It says nothing about that, which is the main open question for a lookup tool returning external data.

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 (wallet) with 100% schema description coverage, so the schema already carries the semantics. The description adds no format guidance beyond '0x wallet address' that the schema already provides; baseline 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?

The first sentence names a specific verb (cross-reference) plus the exact resource (ERC-8004 Identity and Reputation registries) and frames the scope as an external open registry lookup. It distinguishes itself from reputation_status by naming that sibling, though it doesn't disambiguate from the many other reputation_* tools (reputation_query, reputation_leaderboard).

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?

Explicit 'Use when' clause plus an explicit exclusion ('Not for Wicked's own staking data') with a named alternative, reputation_status. Clear routing guidance, though other plausible alternatives (reputation_query, wallet_sanctions_check, wallet_check) go unmentioned.

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