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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them: it scopes the operation to 'pending' drafts and states the access-code requirement, which is an authorization constraint an agent must plan for. It stops short of saying what happens for expired or already-approved drafts.

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 tight sentences: what it reads and what it returns, then the prerequisite. Zero filler and nothing buried.

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 output schema, the description carries the burden of describing return content, and it does so by naming the returned fields and the readiness flag. What it omits are edge-case outcomes (unknown id, expired code, already-approved draft), which keeps it from a 5 for a read tool whose result drives an approval decision.

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 both the uuid id and the one-time accessCode are already fully documented, including their origin in self_register_agent_card. The description's 'Requires the access code' restates mandate-ness but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 (reads) and resource (a pending self-registration draft's current status), then enumerates exactly what is surfaced: metadata, both challenges' pass/fail state, and approval readiness. That enumeration implicitly separates it from the per-challenge check_self_registration_domain_challenge / check_self_registration_endpoint_challenge siblings, which cover only one challenge each.

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 'whether it is ready for the owner's approval' hints at the workflow position (check status before approve_agent_self_registration), but no alternative or exclusion is named explicitly. There is no statement about when to prefer this over the individual challenge-check tools, so usage is only implied.

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