discord_edit_embed

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

The description discloses a key behavioral trait beyond annotations: it's a full replace, not a merge, with omitted fields dropped. Annotations indicate idempotentHint=true, which aligns with this replace behavior, and the description adds the return value ('Returns a confirmation').

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 three sentences, front-loaded with the purpose, immediately followed by a key constraint and behavioral summary. Every sentence adds essential information without redundancy.

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, nested objects, and no output schema, the description covers the core behavior (replace, bot-only, confirmation). It omits potential error cases or response format details, but the schema's thorough documentation compensates.

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 100% description coverage for all 12 parameters, so the schema already provides full meaning. The description adds only the overall 'replace' behavior, not parameter-specific semantics, thus meeting the baseline of 3.

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 embed on a message previously sent by this bot'), specifies the resource (embed on a message), and distinguishes from sibling tools like discord_edit_message (which edits the text content) and discord_send_embed (which sends a new embed).

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 explicitly restricts usage to 'only this bot's messages,' providing clear context. It implies when not to use (on other bots' or user messages) but does not mention specific alternatives or exclusions beyond that.

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