Edit message

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

Annotations already indicate it's a non-read-only, non-destructive operation. The description adds the critical behavioral constraint that only the bot's own messages can be edited, which annotations don't cover. It doesn't disclose potential side effects like rate limits or the 'edited' indicator.

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 extremely concise, using two sentences to convey the primary purpose and a key constraint. No extraneous information.

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?

For a mutation tool with no output schema and five parameters, the description is minimal. It lacks details on edge cases (e.g., empty content?), embeds behavior, or error conditions. However, annotations and schema provide some context, so it's borderline adequate.

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 schema already describes 60% of parameters (channel, guild, embeds). The description adds no additional meaning beyond what's in the schema, not explaining message_id or content semantics. Baseline of 3 is appropriate given partial schema coverage.

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 ('Edit') and the resource ('a message the bot itself sent'). It specifies the limitation to bot's own messages, distinguishing it from other message tools like send_message or delete_message.

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 says Discord does not allow editing others' messages, providing a clear when-not-to-use scenario. However, it doesn't mention alternatives like resending when needing different content or when to use delete+send.

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