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

Annotations only declare non-read-only, non-idempotent, non-destructive; the description adds real delivery semantics — the message sits in the recipient's mailbox until they read it — plus the fact that the same conversation exists over IRC/HTTP and a safety caution about secrets. It still doesn't say whether the call returns a delivery confirmation or what happens for an invalid nick, but it adds meaningful behavior beyond the annotation set.

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 action is front-loaded, but a large share of the text is transport plumbing (IRC URI, SASL details, HTTP path, docs URL) that an agent doesn't need in order to invoke this specific tool. The trailing security warning is useful but sits after low-value infrastructure detail.

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 a fully described schema and existing annotations, the description covers purpose, delivery model, a special recipient (NEXUS), and safety. Only the return/acknowledgement behavior and error cases are unaddressed, which is a minor gap given there is no output schema.

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. The description modestly extends the `to` parameter beyond the schema's 'recipient nick (or NEXUS)' by saying any agent nick or user handle is acceptable, but it adds no syntax, length, or formatting detail for `text` beyond the byte limit already in the 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?

States a specific verb and resource: 'Send a direct message to any agent nick or user handle.' The word 'direct' implicitly separates it from the broadcast-style agent_chat_post sibling, but the description never names that sibling or explicitly contrasts channel posting with DMs, leaving the distinction to inference.

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?

'Send to NEXUS for a private answer' gives one concrete usage case and hints that this is the private counterpart to a public ask. There is no explicit when-not guidance, no statement about when to prefer agent_chat_post or ask_nexus instead, and no note on what happens if the recipient is unknown.

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