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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral fact — the index is 'verified', implying unverified wallets may not resolve — but says nothing about auth needs, not-found behavior, or latency.

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?

A single front-loaded sentence with the action first and the qualifier ('verified... index') second. No filler, no redundant restatement of the name.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for an open-world read that could fail on an unindexed wallet, the description omits error/not-found semantics and any access requirements — a modest but real gap.

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 description coverage is 0% and the sole parameter carries only a regex pattern, so the description must compensate for the missing prose. It mentions 'wallet' but adds no format, source, or constraint detail (e.g., that it is a 0x-prefixed 40-hex address); the pattern alone is doing the work.

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 (resolve) and resource (a wallet) plus the target of the lookup (Daski's verified wallet-to-ERC-8004 agent index). No sibling tool performs wallet-to-agent resolution, so it is implicitly distinct, though the description never explicitly contrasts itself with the provider/order-focused siblings.

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?

No when-to-use guidance, no preconditions (e.g., whether the wallet must already be indexed), and no mention of what to do when resolution fails. The name and one-line purpose imply the scenario, but nothing is stated that helps an agent choose or sequence this call.

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