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

With no annotations provided, the description carries the burden of behavioral disclosure. It helpfully states that the operation is read-only and lists the identity data it resolves across supported chains, but it omits auth requirements, error behavior, rate limits, and whether lookups are on-chain or indexed.

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 definition is a single front-loaded sentence with no filler. The read-only qualifier, resource, returned fields, and chain coverage are all packed efficiently into one statement.

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?

For a simple two-parameter lookup with no annotations or output schema, the description is partially complete: it names the returned identity facets and supported chains. However, it does not fully compensate for the missing schema descriptions, especially the numeric chain_id mapping and agent_id format.

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%, so the description must compensate for the two parameters. It lists supported chain names, which gives some context for chain_id, but does not map those names to numeric chain IDs or explain the expected agent_id format, leaving both parameters materially underspecified.

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 verb and resource: a read-only ERC-8004 identity lookup, and enumerates the exact identity facets returned (owner, agentWallet, registration file, endpoint-domain verification). This clearly distinguishes it from the sibling payment/offer verification tools without needing to name them.

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?

The description explains what the tool does but gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not tell an agent when to choose this lookup versus the sibling verification tools, leaving usage selection implicit.

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