Send IRC message with typing notification

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

Discloses key behaviors beyond annotations: emits typing notification, delay proportional to message length, default 90 wpm, tunable wpm, and returns same response as irc_send_message. This is rich behavioral context not present in annotations.

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?

Four concise sentences, front-loaded with core purpose, then usage guidance, then return value. No redundant or filler content.

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?

Covers purpose, usage, delay behavior, and return, but with 7 parameters and no schema coverage, the missing parameter semantics and potential text/lines distinction make it incomplete. The tool is not fully self-contained for correct invocation.

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%, but description only explains wpm and implies message length. It leaves text, lines, notice, account, and in_reply_to undocumented. The 'same as irc_send_message' reference applies only to return value, not parameters, so semantic gap is significant.

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?

Description clearly states the tool sends an IRC message with a typing notification and delay, distinguishing it from irc_send_message. The verb 'send' and resource 'message' are explicit, and the sibling differentiation is present.

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?

Explicitly says 'Use this for direct conversation where a natural typing indicator is desirable' and contrasts with irc_send_message for immediate delivery. Provides clear when-to-use and when-not-to-use guidance.

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