discord_send_embed

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

Discloses that it requires Send Messages and Embed Links permissions, returns the new message ID, and implies a write operation. This complements annotations (readOnlyHint=false, destructiveHint=false) by adding concrete details.

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?

Three concise sentences: one for purpose, one for usage guidelines, one for permissions and return value. No fluff, front-loaded with key information.

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 11 parameters (100% schema coverage) and no output schema, the description sufficiently covers purpose, usage, permissions, return value, and key embed components. No missing critical 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?

Schema coverage is 100%, so baseline is 3. The description adds a high-level list of embed components ('title, description, color, fields, author, footer, images, timestamp') that provides an overview beyond the individual parameter descriptions.

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?

Clearly states it sends a single rich embed, distinguishes from siblings (discord_send_message for plain text, discord_send_multiple_embeds for multiple embeds), and mentions required permissions.

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 tells when to use this tool vs alternatives: 'Use discord_send_message for plain text, or discord_send_multiple_embeds to send several embeds at once.' Also states required permissions.

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