discord_send_message

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

The description adds the behavioral requirement 'Writes must be enabled locally,' which is a meaningful environmental constraint not captured in the annotations. It also clarifies that the action is performed as the configured bot. However, it does not detail side effects or rate limits, though annotations already cover read/write and idempotency.

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 a single sentence of 13 words, front-loaded with the core purpose and followed by a key prerequisite. No information is redundant or extraneous.

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 simple message-sending tool, the description covers the core function and a critical local write requirement. It does not address return values or edge cases, but given the simple nature and existing annotations, it is reasonably complete for an agent to select and invoke the tool.

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 low (only channelId has a description), so the description helps by implying that content is the message text and replyToMessageId is for replies. Yet it does not explicitly map parameters or explain optional behavior beyond what the schema provides.

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 action: 'Send a Discord message or reply as the configured bot.' It uses a specific verb and resource, and the wording distinguishes it from sibling tools like discord_list_channels or discord_read_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 mentions the prerequisite 'Writes must be enabled locally,' which is useful context, but it does not explicitly state when to use this tool versus alternatives or provide any exclusions. Usage is implied as the tool for sending messages, but no alternative guidance is given.

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