discord_edit_dm_embed

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

With no annotations, the description must disclose all behavioral traits. It reveals that omitted fields are removed (destructive), but fails to mention error cases, permission requirements, rate limits, or what happens if the message doesn't exist or is not an embed.

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 a single, well-structured sentence that conveys the essential information without unnecessary words. It is front-loaded and efficient.

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 13 parameters (including nested objects) and no output schema, the description is too sparse. It does not explain how to use nested fields like 'fields' and 'author', nor does it describe return values or error behavior.

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 62%, and the description does not add any parameter-level context beyond what the schema already provides. It meets the baseline but does not compensate for the uncovered parameters.

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 verb 'edit', the resource 'embed in a DM', and the critical nuance that omitted fields are removed. This distinguishes it from sending a new embed or editing the DM message itself.

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 explains the partial update vs replacement behavior, which is a key usage guideline, but it does not explicitly state when to use this tool versus siblings like discord_edit_dm or discord_send_dm_embed, nor does it mention prerequisites like the message must be a bot message.

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