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 semantics, that it drains ONLY the pinned rendezvous relay and stops at the matching DM, that mismatched DMs are deleted and NACK'd without revealing the expected phrase, and that the grant is self-verifying with nothing stored server-side. 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-loaded with purpose, then the precondition, then the mechanics, then the return contract. Every sentence is functional, though the prose is denser than strictly needed and the parenthetical/markdown emphasis adds minor noise.

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 flow-completing, mutation-adjacent tool with an output schema already covering return shape, the description supplies everything else an agent needs: prerequisites, ordering, misuse consequences, and the downstream obligation to persist the returned dpop_token.

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 meaning beyond the schema: it explains the naming key '(patron_npub, dpop_token)' and pins the provenance of dpop_token to the value returned by request_npub_proof. That provenance is not in the schema and is operationally essential.

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') and situates it within the npub-OWNERSHIP-PROOF flow, explicitly naming the counterpart tool receive_credentials. An agent can distinguish it from siblings 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 explicit preconditions ('Call this only after the user confirms they have replied'), names the prerequisite tool (request_npub_proof for the dpop_token), and states exclusions ('Do NOT poll, loop, or retry'). Nothing is left to inference.

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