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

With no annotations provided, the description carries the full behavioral burden. It discloses important limitations: data is text/identifier matched, not verified identity or reputation, and sources 'degrade individually and honestly.' It also lists the source categories transparently, though it does not state whether the operation is read-only or describe any authentication or rate-limit behavior.

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 is compact and front-loaded, covering the main purpose in the first sentence and then adding important limitations without excess fluff. The phrase 'sealed first-report sea protests' is somewhat jargon-heavy, but overall each sentence contributes useful information.

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?

The description lists multiple data sources and limitations, which is helpful, but there is no output schema and no return-shape explanation. An agent may still be uncertain how the results are structured, how sources are represented, or how matching behaves across the different source types.

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 100%, so the parameter semantics are already well documented in the schema. The description adds context about matching behavior and source degradation, but it does not provide additional parameter-level detail beyond what the schema already states for query, chain, limit, and agent_id.

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 names a specific action (attestation about another agent) and enumerates the concrete data sources involved: ERC-8004 registry events, liveness probes, incident candidates, sealed first-report sea protests, and x402 payment observations. It also explicitly distinguishes itself from verified identity and reputation scoring, which helps separate it from sibling tools like verified_track_record or seal_lookup.

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 gives clear context on what the tool is for and what it is not for, stating 'Text/identifier matching — not verified identity, not a reputation score.' It implies this is for attestation-style lookups rather than verified identity or reputation tasks, but it does not name specific sibling tools or provide explicit when-to-use/when-not-to-use routing.

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