discord_send_embed

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

With no annotations provided, the description carries the full burden. It successfully documents the fallback behavior for 'guild_id' to DISCORD_DEFAULT_GUILD_ID, but omits critical behavioral traits like required permissions, rate limits, error handling, or whether this creates a persistent public message.

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 well-structured with a clear purpose statement followed by an Args block. Given the necessity to document 7 parameters with zero schema coverage, the length is appropriate and every line adds necessary value.

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 description adequately covers the complex input schema (including the nested fields structure), but lacks information about return values (no output schema exists), error scenarios, or side effects that would be expected for a messaging tool with no annotations.

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 input schema has 0% description coverage. The Args block compensates perfectly by documenting all 7 parameters with clear semantics and useful examples (e.g., '3447003 for blue' for the color parameter, and structure details for the fields array).

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 sends a 'rich embed message' (specific verb + resource) to a Discord channel. It implicitly distinguishes from sibling 'discord_send_message' by specifying 'rich embed', though it doesn't explicitly contrast the two 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 provides a conditional usage rule for 'guild_id' (required when channel is a name), but fails to specify when to choose this tool over the plain 'discord_send_message' alternative or mention any prerequisites like bot permissions.

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