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

No annotations are provided, so the description carries full behavioral burden and does so richly: it discloses the retrieval is deterministic and one-shot, that it drains ONLY the pinned rendezvous relay, that mismatched DMs are deleted and NACK'd without revealing the expected phrase, that it is free, and that the returned dpop_token must be persisted and reused. Nothing critical about side effects or state is left implicit.

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 core purpose and the strict preconditions are front-loaded, and every section earns its place. It is on the long side with some narrative flourish and RST markup, but there is little outright filler.

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 need not be spelled out, yet the description still clarifies the shape and downstream obligation of the returned grant envelope. For a flow-bound, mutation-ish retrieval tool with no annotations, the definition is complete enough to call 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 genuine meaning: it explains that dpop_token is the value returned by request_npub_proof and that the response is keyed on (patron_npub, dpop_token). That linkage between the two required parameters is not derivable from the schema alone.

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 opening sentence states a specific verb and resource ('Receive npub ownership confirmation from a patron') and explicitly positions the tool within a named flow, identifying its counterpart sibling ('the credential-delivery counterpart is receive_credentials'). An agent can distinguish it from the many other cypher_* tools 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?

Usage is tightly bounded: 'Call this only after the user confirms they have replied' plus explicit prohibitions ('Do NOT poll, loop, or retry') and a stated consequence for misuse ('If called before the user replies, their message will never be found'). This is the exact when/when-not guidance an agent needs for a one-shot retrieval tool.

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