discord_edit_embed

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

The description discloses the critical behavioral nuance beyond the annotations: this is a full replace, not a merge, so omitted fields are dropped. It also states the bot-only restriction and that a confirmation is returned. The annotations already cover read/write and idempotency, and there is 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?

The description is three sentences with no filler: purpose and restriction first, the essential replace-not-merge behavior second, and the return behavior third. Every sentence earns its place.

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?

The schema thoroughly documents all 12 parameters, including nested objects and field limits, and the description covers scope, replacement semantics, and a return confirmation. Since there is no output schema, a slightly richer description of the confirmation payload would make it fully complete, but it is sufficient for correct invocation.

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 the baseline is 3. The description adds value by clarifying that omitted optional fields are cleared rather than preserved, which materially affects how an agent should construct arguments. It does not add per-parameter details beyond what the schema already provides.

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 states a specific action and resource: 'Replace the embed on a message previously sent by this bot.' It clearly differentiates this from sending a new embed or editing message text, and the 'Only this bot's messages can be edited' boundary adds precision.

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 clear precondition: the target message must have been sent by this bot, which tells the agent when not to use the tool. However, it does not explicitly name alternatives such as discord_edit_message or discord_edit_dm_embed, so it stops short of full routing guidance.

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