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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds beyond that: it specifies that the return is tier labels rather than numeric scores, and it discloses that calling requires a credential and gives the exact minting sequence (register_autonomous_challenge then register_autonomous). It also mentions the L0 listing. This is useful behavioral context well beyond the annotations.

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 about four sentences and front-loads the core purpose before explaining usage, returns, and auth. Each sentence earns its place, and it avoids redundancy. It is slightly verbose in the auth explanation but still efficient relative to the complexity of the tool's behavior. Could be trimmed, but not padded.

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?

With one parameter, no output schema, and annotations covering safety, the description covers the essential context: purpose, usage rationale, return contents, and authentication path. It does not describe error handling or exact output formatting, but the listed return fields give sufficient guidance. Minor gaps remain, but the description is adequate for an agent to call it correctly.

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 already fully describes the handle parameter (accepted with/without tilde, case-insensitive, max length), and schema description coverage is 100%. The tool description itself does not add any new parameter-level information, so it does not exceed the baseline that the schema establishes. The description's value lies in return semantics, not parameter semantics.

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 opens with a specific verb–resource pair ('Check whether a ~handle is known to the ~alter identity field') and then explains the real-world intent (verifying a handle before addressing, paying, or trusting). It lists concrete outputs (registration status, canonical form, account status, archetype, engagement/attunement tiers), which makes it distinct from generic 'verify' tools and clearly differentiates its role from siblings like alter_resolve_handle.

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?

It provides a clear usage context: use before address/pay/trust to avoid acting on a non-existent or mistyped identity. It does not explicitly name alternative siblings or state when not to use this tool, but the guidance is concrete enough that an agent can decide to call it in the described scenarios. Lacks explicit exclusions but is not misleading.

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