discord_edit_message

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

With no annotations provided, the description carries the full burden. It discloses that editing is limited to bot messages only, which is a crucial behavioral constraint. However, it doesn't mention authentication requirements, rate limits, or what happens when editing fails, leaving some behavioral aspects unclear.

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 with zero waste: the first states the purpose and scope, the second adds a critical exclusion. Every word earns its place, and the most important information (what it does and what it doesn't do) is front-loaded.

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 annotations and no output schema, the description provides essential context about limitations (bot messages only) but lacks details on error conditions, return values, or side effects. Given the complexity of editing messages in Discord, more behavioral context would be helpful.

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 0%, so the description must compensate. It mentions that you can 'edit content and embeds,' which maps to two of the four parameters (content, embeds), adding meaning beyond the bare schema. However, it doesn't explain channel_id or message_id parameters, leaving half the parameters without semantic context.

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 specific action ('Edit a message') with the resource ('the bot previously sent'), distinguishing it from sibling tools like discord_delete_message or discord_send_message by specifying it's for editing existing bot messages only.

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?

It explicitly states when to use this tool ('Edit a message the bot previously sent') and when not to use it ('Cannot edit other users' messages'), providing clear boundaries that differentiate it from alternatives like discord_send_message for new messages.

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