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

With readOnlyHint=false the annotations only signal that this writes something; the description supplies the substance: it records the claim, records what this connection showed, records that nothing is verified, and grants no authority. That is a genuinely informative write-side contract that goes well beyond the annotation flags, and it is consistent with destructiveHint=false.

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?

Two compact sentences plus a front-loaded bracketed routing tag; every clause carries weight and the key scoping caveat is stated twice for emphasis. Slightly repetitive in the token/admission/authority wording, but no dead weight.

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?

There is no output schema and the tool is conceptually simple, so the description's behavioral contract plus the fully documented schema covers what an agent needs to call it. It omits edge details such as whether repeat calls overwrite prior claims, which keeps it from a 5.

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 all five parameters (including the meaning of 'principal' as UNVERIFIED) are already documented in the schema. The description adds no per-parameter syntax or constraints beyond that, which is the expected baseline when the schema does the heavy lifting.

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 gives a specific verb and resource ('State who you claim to be' / record an identity claim) and explicitly negates the authority-granting behavior of siblings like atlas.authenticate, atlas.enroll, and atlas.use ('no token, no admission, no authority'). It does not name a sibling directly, so it falls just short of a 5, but the contrast is unambiguous.

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 '[OPEN: no admission needed]' tag establishes the condition under which this tool is the right choice: when the caller has not been admitted. The repeated 'grants no token, no admission, and no authority' clause implicitly routes agents seeking real authority to authenticate/enroll. No explicit when-not statement is given, so 4 rather than 5.

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