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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description is not required to establish safety. It still adds genuine value beyond them: it rules out hidden quota/session/cache/job writes and, critically, warns that an unavailable result must not be interpreted as anonymous or free-fallback access — a failure-mode caveat no annotation conveys.

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 sentences, front-loaded with the return contents before the negative scope and the fallback caveat, with no filler. The four-item negative list ('quota/session/cache/job') is slightly dense, and 'keyed pseudonymous principal reference' is jargon, but both carry information rather than restating the name.

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 no input schema and no output schema, the description must carry the return contract, and it does so by naming each returned field. It stops short of explaining what the 'tier' values or 'owner-IP-gate disposition' states mean, so an agent knows the shape but not the value vocabulary.

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 tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly implies the subject is always the calling request rather than a supplied target, which is the only semantic an agent needs here.

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?

States a specific verb and resource ('Read the effective authentication context for this request') and then enumerates exactly what that context contains: tier, owner-IP-gate disposition, pseudonymous principal reference, server version, observation time. The negative scope statements ('Performs no target checks or quota/session/cache/job writes') further separate it from every domain/DNS scanning sibling in the list.

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 phrase 'for this request' and the no-side-effect clause imply the tool is a cheap self-introspection call safe to make before or alongside other work, but there is no explicit 'use this when' or 'use this instead of X' guidance. An agent can infer the situation but must do the inference itself.

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