discord_send_dm_embed

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

Annotations indicate write operation (readOnlyHint=false) and non-destructive mutation. The description adds the requirement that the bot shares a server and the user allows DMs, and states it returns a message ID. However, it could mention that sending a DM may create a DM channel, or that the embed can contain up to 25 fields (though schema covers this). Still, it adds meaningful context beyond annotations.

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: first states purpose, second gives usage alternatives, third lists prerequisites and return value. Every sentence adds value with no repetition or fluff. Front-loaded with the core action.

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 the 12 parameters fully described in schema and the absence of output schema, the description covers essentials: purpose, alternatives, prerequisites, return value. It could include a mention of embed limitations (e.g., field count) but schema already handles that. Overall complete for complex 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 has 100% coverage with detailed descriptions for all 12 parameters. The description adds no additional parameter-level information beyond what's in the schema. Baseline score of 3 is appropriate as the schema already documents semantics fully.

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 as a private DM to a user. It explicitly distinguishes from sibling tools: discord_send_dm for plain text DMs and discord_send_embed for channel embeds. The verb-resource pairing is precise.

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 explicit guidance on when to use this tool versus alternatives ('Use discord_send_dm for plain text, or discord_send_embed to post an embed in a channel'). It also lists prerequisites for usage: shared server and user DM settings. This fully addresses when and when not to use the tool.

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