identity__list_registrations

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

No annotations are provided, so the description carries the full burden. It states 'List' which implies read-only, but it does not explicitly confirm no side effects, no authentication requirements, or data freshness. Since listing is inherently non-destructive, a score of 3 is adequate given the context.

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 a single sentence plus a brief prefix. Every word is functional: 'List registrations, optionally filtered by status (ACTIVE|REVOKED).' No extraneous information, and the key action is front-loaded.

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 tool has one parameter and no output schema. The description covers the action and the parameter, but it does not hint at the return structure (e.g., list of registration objects or IDs). Given the tool's simplicity, it is minimally adequate but not fully complete.

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?

The input schema has 0% description coverage, but the description adds meaning by specifying the valid values 'ACTIVE|REVOKED' for the status parameter and implying it is optional. This compensates for the schema's lack of documentation, though it does not describe other possible values or the null case.

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 clearly states the action 'List registrations' and specifies an optional filter by status (ACTIVE|REVOKED). The resource is registrations, and the verb is list. It distinguishes from siblings like identity__register_agent (create) and identity__revoke_agent (destructive).

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 implies usage for listing registrations, but it does not differentiate from the sibling erc8004__list_registrations, which has an identical name and purpose. There is no guidance on when to use this tool versus that one, nor when to apply the status filter.

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