discord_send

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

No annotations are provided, so the description carries the full burden. It states the action and the reply option, but does not mention potential side effects like permissions failures, rate limits, or whether the message appears as the bot. For a simple send, this is acceptable but not highly 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 two sentences long and directly to the point. Every clause adds useful information—the primary action and the optional reply capability—with no unnecessary fluff.

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?

Given the tool's simplicity, the description is sufficiently complete. It covers the main action, the target channel, and the reply feature. It does not specify return format or error behavior, but those are not critical for a send operation in this context.

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?

The schema defines three parameters with no descriptions. The tool description clarifies channelId as a 'specified Discord text channel' and replyToMessageId as 'reply to another message by providing its message ID'. The 'message' parameter is self-explanatory. Coverage is good but not exhaustive.

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 clearly states the tool's function: sending a message to a Discord text channel. It distinguishes itself from siblings like discord_send_webhook_message (which sends via webhook) and discord_edit_message (which modifies existing messages).

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 when to use it (for sending a message to a channel) and mentions the optional reply feature. It does not explicitly contrast with alternatives, but the sibling names make the primary use case obvious.

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