buzz_reply

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

No annotations exist, so the description carries the full burden. It exceeds basic expectations by disclosing the NIP-10 threading behavior via marked e-tags (root/reply), the alias behavior for `text`/`message`, how to mention agents with @Name, and that `attachment` is a local file path to upload. It omits permission/auth requirements and return behavior, which keeps it from a 5.

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 two dense, information-rich sentences with no filler. It front-loads the core purpose, then packs prerequisites, aliasing, threading behavior, mention syntax, and attachment semantics in a logically ordered, efficient way.

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 write action with no annotations and no output schema, the description is largely complete: it identifies required parameters, tells where the event id comes from, explains the thread behavior, and covers optional fields. Minor gaps remain around acceptable channel identifiers, likely authentication/login requirements, and expected confirmation/response behavior, but an agent has enough to invoke it correctly.

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 60%, and the description adds meaning beyond the schema by clarifying that `event` is the id from buzz_read, that `text` carries the reply body with `message` as an accepted alias, and that `attachment` is a local file path. The only notable gap is that `channel`'s expected format is not specified, but the description still meaningfully compensates for schema gaps.

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 opens with a specific verb and resource: 'Reply to a message in a channel'. It adds a precise protocol-level qualifier ('threaded per NIP-10 (kind 9)') and the required context (channel + event), which clearly separates this from sibling tools like buzz_post, buzz_forward, and buzz_react.

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 clear context for when to use this tool: when replying to an existing message, requiring both `channel` and `event` (explicitly the `<id>` from buzz_read). It does not explicitly name alternative tools or say 'use buzz_post instead for new top-level messages', so it stops short of a 5, but the invocation condition is unmistakable.

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