discord_edit_message

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

Discloses key behaviors: edits only bot messages, fails on others, returns edited message ID, works in text channels and threads. Annotations already indicate non-read-only, non-destructive, idempotent; description adds constraints and scope. Minor omissions like rate limits or side effects prevent a 5.

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?

Three concise sentences, front-loaded with purpose. No waste; every sentence adds value. Efficient structure.

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?

Simple tool with few parameters and no output schema. Description covers purpose, constraints, return value, and alternative tool. Complete for its complexity.

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 covers all 3 parameters with descriptions (100% coverage). The description reinforces message_id constraint (must be bot message) but does not add new parameter details. Baseline 3 applies; marginal added value.

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 tool edits text content of a message sent by the bot, distinguishing it from discord_edit_embed for embeds. It specifies the resource (message text) and action (edit), and notes Discord's restriction to bot-authored messages.

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?

Explicitly states when to use (edit bot's message text) and when not to (non-bot messages). Points to alternative tool discord_edit_embed for embeds. Provides clear guidance on channels/threads compatibility.

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