discord_send_dm_embed

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

Annotations already flag this as a non-read, non-idempotent write, so the bar is lower. The description adds genuine value beyond that: the DM permission prerequisites, the open-world dependency on recipient settings, and the return value ('Returns the new message ID') which is otherwise undisclosed since there is no output schema. The description is consistent with all annotation hints — no contradiction.

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 sentences, each earning its place: core purpose, sibling routing, then prerequisites plus return value. Front-loaded and free of filler or restatement of schema content.

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?

Complete for a complex 12-param tool with nested objects and no output schema. The description covers purpose, alternative routing, prerequisites, and the return value (compensating for the missing output schema). Failure conditions are implied by the stated prerequisite about DM permissions, which is adequate.

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 100% — all 12 parameters, including nested author and fields objects, have meaning-bearing descriptions in the schema. The description itself adds no parameter-level detail, but with full coverage it doesn't need to, so baseline 3 applies.

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?

States a specific verb+resource — 'Send a rich embed as a private direct message to a user' — and immediately distinguishes itself from siblings by naming discord_send_dm (plain text) and discord_send_embed (channel embed). An agent can tell this apart from the sibling send tools without opening the schema.

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 provides selection criteria: use discord_send_dm for plain text, discord_send_embed for embeds in a channel, and this tool for embeds delivered as DMs. It also discloses prerequisites the agent must verify before calling — the bot must share a server with the recipient and the user must allow DMs from server members — so the agent knows when the call will likely fail.

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