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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose a side effect ('Sends a welcome DM'), a delivery mechanism ('Secure Courier channel'), and the cost ('Free'). However, it does not explain whether a persistent channel is created, what the credential template contains, or whether any prerequisite state is required.

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 short and front-loads the primary action, with the concrete outcome in the second sentence and the cost note at the end. The 'Free.' fragment is slightly abrupt but still useful and does not waste words.

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?

Although the tool is simple with one optional parameter and an output schema, the description omits any explanation of the only parameter and gives no usage guidance relative to related credential tools. An agent could understand the general behavior but cannot confidently determine what to supply for sender_npub.

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%, and the description never mentions 'sender_npub' or explains its purpose, default behavior, or optionality. The single parameter is completely undocumented by both schema and description, so an agent cannot reason about what value to provide.

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 specific action ('Open a Secure Courier channel') and a clear resource ('patron credential delivery'), and further clarifies the concrete effect ('Sends a welcome DM with a credential template to the patron'). It is more specific than the tool name, though it does not explicitly distinguish itself from closely named siblings like roastify_receive_patron_credentials or roastify_request_credential_channel.

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 implies the tool should be used when a patron needs to receive credentials through a welcome DM, but it gives no explicit guidance about when to choose this tool over alternatives such as roastify_receive_patron_credentials or roastify_request_credential_channel. There is no when-not-to-use or exclusions.

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