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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context by noting that the access code is required and specifying what the status includes (metadata, challenge states, readiness). This goes beyond the annotations, though it does not discuss error behaviors or rate limits, which are not critical for a read-only operation.

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 concise, consisting of two short sentences. It front-loads the core purpose ('Reads a pending self-registration draft's current status') and then adds relevant details (challenges, readiness, access code requirement). Every sentence contributes useful information without redundancy or fluff.

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, so the description is responsible for indicating what the tool returns. It does so by listing the status components (metadata, challenge pass/fail states, readiness). It also notes the access code requirement. However, it does not mention error cases or the exact return structure, which would make it fully complete, but for a simple read operation with strong annotations, it is sufficiently informative.

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 has 0% description coverage, so the description must compensate. It explicitly explains that the accessCode is required, but it does not directly explain the 'id' parameter, though it is implied to be the draft's ID from the phrase 'pending self-registration draft'. This partial explanation provides some meaning but leaves the id parameter under-specified, so a score of 3 is appropriate.

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 'Reads a pending self-registration draft's current status' with a specific verb and resource, and elaborates on the exact status components (metadata, both challenges' pass/fail state, readiness for approval). This distinguishes it from sibling tools like check_self_registration_domain_challenge (which checks individual challenges) and approve_agent_self_registration (which approves).

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 description provides clear context by stating the tool requires the access code and reads the status of a pending draft. However, it does not explicitly mention when to use this tool over sibling tools like check_self_registration_domain_challenge or update_self_registration, nor does it provide exclusions. Thus it gives clear context but no explicit alternative comparisons, missing the top score.

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