Edit message

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the mutation nature is known. The description adds valuable behavioral context by explaining the platform constraint about only bot-authored messages being editable, which is not captured in annotations or schema.

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 two sentences, with the primary action in the first sentence and the crucial restriction in the second. Every word serves a purpose, and it is front-loaded with the core purpose.

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 tool's moderate complexity and the presence of rich sibling tools, the description covers the most important contextual constraint (bot-only editing). It does not discuss return values, but no output schema exists and the tool's behavior is straightforward enough that this is not a major gap.

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 description provides no parameter-level guidance. The schema covers 60% of parameters, leaving content and message_id undocumented. While these names are somewhat self-explanatory, the description could have clarified that content or embeds can be supplied as the replacement, but it does not.

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 uses a specific verb and resource: 'Edit a message the bot itself sent.' This clearly states the tool's action and target, and the added restriction distinguishes it from broader 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 states the key limitation: Discord does not allow editing anyone else's messages, regardless of permissions. This tells the agent when this tool can be used (only for bot-sent messages) and implicitly that alternatives must be considered for other messages. However, it does not name specific alternative tools.

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