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

With no annotations, the description carries the full behavioral burden and does so richly: deterministic one-shot retrieval, drains only the pinned rendezvous relay, deletes and NACKs mismatched DMs without revealing the expected phrase, no retry, and the consequence of premature calling. It also discloses the returned artifact (an Operator-signed proof grant envelope) and the caller obligation to persist it.

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-loaded with the purpose and the gating condition, then structured with bolded cues. It is on the long side for a 2-parameter tool and slightly restates the 'call only after reply' rule implicitly in the failure sentence, but nearly every sentence adds actionable detail.

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, yet the description still usefully characterizes the returned grant and the caller's obligation to reuse it. For a complex multi-step, stateful flow with no annotations, it supplies everything an agent needs to invoke correctly and to handle the result.

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 real meaning: it defines dpop_token as the value returned by request_npub_proof and frames the pairing as '(patron_npub, dpop_token)' deterministic naming. That is more than the schema conveys.

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 ('Receive npub ownership confirmation from a patron') and explicitly positions itself in a named flow, calling out both the counterpart tool (receive_credentials) and the prerequisite (request_npub_proof). An agent can place it precisely among the many siblings without opening a 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?

Explicitly says 'Call this only after the user confirms they have replied' and 'Do NOT poll, loop, or retry.' It names the alternative that precedes it (request_npub_proof) and the sibling that covers the other half of the flow (receive_credentials), so when-to-use and when-not are both covered.

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