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

With no annotations, the description carries the full burden and delivers: one-shot deterministic retrieval, relay-draining scope, mismatch handling (delete + NACK without revealing the phrase), failure mode if called early, the token lifecycle, and that the proof is stored as a hash while the raw token is never stored. This is unusually rich behavioral disclosure.

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 purpose, then the critical precondition in bold, then mechanics and token lifecycle. It is somewhat long, but nearly every sentence conveys a distinct operational constraint, so little is wasted.

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?

For a two-parameter tool with an output schema, the description covers the flow position, prerequisite, timing constraint, failure behavior, and return-token handling. Nothing an agent needs to call it correctly is missing.

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 schema documents both params; the description still adds value by explaining that dpop_token is the value returned by request_npub_proof and must be persisted and re-passed on every subsequent paid call. That lifecycle meaning exceeds the schema text.

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+resource ('Receive npub ownership confirmation from a patron') and situates it in a named flow, explicitly distinguishing it from its counterpart 'receive_credentials'. An agent can identify the tool without opening the 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') and an explicit anti-pattern ('Do NOT poll, loop, or retry'), and names the prerequisite tool 'request_npub_proof'. The when/when-not conditions are fully spelled out.

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