identity__list_registrations

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

With no annotations, the description must fully disclose behavior. It mentions optional status filtering with valid values (ACTIVE|REVOKED), which is helpful. However, it does not state whether the operation is read-only, if pagination exists, or any ordering of results. This is adequate for a simple list but not fully transparent.

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 extremely concise: two sentences with no filler. The context bracket is front-loaded, and every word adds value. No redundancy or unnecessary detail.

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?

Given the simplicity (1 parameter, no output schema, no annotations), the description covers the essential purpose and parameter semantics. However, it omits any description of the return value, which would be helpful for an agent to understand what information the registration list contains.

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. It clearly explains the 'status' parameter, listing the allowed values (ACTIVE|REVOKED) and that it's optional. This adds meaningful guidance beyond the schema's minimal type definition.

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 tool lists registrations with optional status filtering. The bracket prefix '[identity — verifiable agent identity + capability discovery]' provides context, distinguishing it from other identity tools like identity__register_agent or identity__resolve_agent. However, it could be more precise about what constitutes a 'registration' in this context.

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 explicit guidance on when to use this tool versus alternatives such as identity__discover_agents or erc8004__list_registrations. The description only implies the scope via the identity prefix, but fails to specify use cases or exclusions.

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