Post a message to a channel. Provide content (text up to 2000 chars), embeds (rich JSON), or both. reply_to makes it a reply.
Bulk support: accepts channel_ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| embeds | No | ||
| account | No | ||
| content | No | ||
| reply_to | No | ||
| channel_id | Yes | ||
| channel_ids | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations (all false), the description adds constraints like 2000-char limit, embeds as rich JSON, reply_to, and channel_ids for batch. However, it does not disclose auth requirements, rate limits, or error behavior.
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 concise sentences, front-loaded with the core action and efficient in communicating both standard and bulk usage without unnecessary 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?
The tool has 6 parameters, no output schema, and minimal annotations. The description covers the main use case and bulk option but leaves the 'account' parameter unexplained and lacks guidance on error handling or failure scenarios. Adequate but with clear gaps.
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?
With 0% schema description coverage, the description explains content, embeds, reply_to, and channel_ids, but omits the 'account' parameter entirely. It adds meaning for most params but not all.
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 'Post a message to a channel' with a specific verb and resource, and lists key parameters. It distinguishes from siblings like discord_send_dm by targeting channels, and from edit/delete message tools.
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 usage for channel messaging and mentions bulk support, but does not explicitly state when to use this instead of alternatives like discord_send_dm, nor does it provide exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.