discord_edit_dm_embed

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

Beyond annotations (idempotentHint=true, destructiveHint=false), the description adds important behavioral information: that it's a full replace (not merge) and it returns a confirmation. It also clarifies that only the bot's own messages can be edited, which is not captured by 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?

Two sentences deliver all essential information without any redundant or vague language. Every word serves a purpose, making it highly efficient for an AI agent to parse.

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 tool's complexity (13 parameters, nested objects) and no output schema, the description covers purpose, constraints, and behavior sufficiently. It could mention that user_id and message_id are required, but the schema already handles that, keeping the description appropriately focused.

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%, so each parameter is already documented in the schema. The description adds value by explaining the overall replace/merge behavior, which affects how omitted fields are handled, but does not add per-parameter details beyond the schema.

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 action (replace), the target resource (embed on a DM message), and a key condition (previously sent by this bot). It effectively distinguishes from similar sibling tools like discord_edit_embed (which likely targets guild messages) and discord_send_dm_embed (send vs edit).

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 critical constraint (only bot's own messages) and behavior (full replace, not merge) but does not explicitly guide when to use this tool over alternatives like discord_edit_embed or discord_edit_message. Usage is implied rather than explicitly stated.

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