discord_send

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

With no annotations, the description carries the full burden but discloses nothing about authentication (bot token requirement), rate limits, message length limits, or whether embeds render alongside content. Only the side effect of posting is implied by the verb.

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?

A single front-loaded sentence with no filler, but it is under-specified rather than efficient; brevity here costs information rather than saving it.

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?

No output schema, no annotations, and four parameters with sparse schema descriptions mean the definition is missing essentials: auth expectations, message/embed constraints, and the result of the send. The one sentence cannot cover a messaging mutation 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 description coverage is only 25% — just bot_token is documented in the schema. The description adds nothing about content length limits, the expected structure of the embeds array (whose items are untyped), or channel_id format, leaving three of four parameters semantically thin.

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 gives a specific verb+resource ('Send a message to a Discord channel'), which clearly separates it from read-side siblings like discord_read and discord_search. It does not explicitly mention threading or reaction variants, but the core action is unambiguous.

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?

There is no guidance on when to prefer this over siblings such as discord_thread (thread replies), discord_react, or telegram_send. The agent must infer channel messaging from the verb alone.

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