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

With no annotations, the description carries the full behavioral burden and largely succeeds: it discloses deterministic one-shot retrieval, that the tool drains only the pinned rendezvous relay, stops at the matching DM, and should not be polled or retried. Some jargon ('pinned rendezvous relay', 'Secure Courier') is unexplained, so it is informative but not fully transparent.

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 description is compact, front-loaded with the core action, and each sentence serves a purpose. The awkward phrase 'name the response with' and the heavy relay-specific jargon cost some clarity, but there is minimal wasted text.

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?

The output schema covers return values, and the description explains the one-shot mechanics and no-retry rule. However, it assumes background knowledge about the Secure Courier, pinned rendezvous relay, how the channel is established, and what to do if no matching DM exists; a prior request_patron_credentials step is implied but never stated.

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 description coverage is 0%, so the description is the only source of parameter meaning. It explains that sender_npub and dpop_token identify the retrieval and that credential_card is an alternate ncred1... path not requiring dpop_token. It does not detail all formats or constraints, but it compensates well for the empty schema.

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 description states a clear action ('Pick up patron credentials from the Secure Courier') and distinguishes two retrieval modes: sender_npub/dpop_token or credential_card. It adds behavioral specifics like 'deterministic, one-shot retrieval' that separate it from generic receive tools, though it does not explicitly name sibling tools.

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?

The description gives operational guardrails such as 'Do NOT poll or retry' and explains the credential_card alternative, which helps an agent know how to invoke it. However, it never states when to choose this tool over sibling tools like roastify_receive_credentials or roastify_request_patron_credentials, leaving some selection to inference.

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