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

No annotations are provided, so the description carries the full burden and it does so richly: one-shot deterministic retrieval, drains only the pinned rendezvous relay, deletes and NACKs mismatched DMs without revealing the expected phrase, and the failure mode if called too early. It also discloses auth-relevant behavior (the signed DM proves ownership) and that the returned grant is self-verifying and nothing is stored.

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?

Front-loads the core action in the first sentence and organizes the rest into flow, preconditions, and return semantics. It is dense and somewhat long, but nearly every clause carries operational information; the size is justified by the complexity of a one-shot, token-issuing flow.

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?

An output schema exists so return values needn't be documented, yet the description still explains the returned proof-grant envelope and its reuse contract. Combined with the preconditions, failure modes, and token binding, an agent has everything needed to invoke 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?

Schema coverage is 100%, so the baseline is 3, but the description adds lifecycle meaning beyond the schema: it explains that `dpop_token` is the value returned by `request_npub_proof` and must be passed on every subsequent paid call, and that the name is keyed on `(patron_npub, dpop_token)`.

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 the specific verb+resource ('Receive npub ownership confirmation from a patron') and names the flow it completes ('npub-OWNERSHIP-PROOF'), explicitly identifying the credential-delivery counterpart `receive_credentials`. An agent can distinguish it from siblings like `request_npub_proof` and `check_proof_status` without opening any schema.

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?

Gives an explicit precondition ('Call this only after the user confirms they have replied'), an explicit prohibition ('Do NOT poll, loop, or retry'), and points to the tool that supplies the input (`request_npub_proof`). It also names the sibling counterpart for the alternate flow, leaving nothing to inference.

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