discord_delete_message

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: the destructive nature of deletion, permission requirements (Manage Messages for others, self-deletion allowed), and the audit log implication via the 'reason' parameter. This covers safety and authorization aspects well, though it lacks details on error handling or rate limits.

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 front-loaded with the core purpose in the first sentence, followed by essential usage context in the second. Both sentences earn their place by providing critical information without redundancy, making it efficient and well-structured.

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 complexity (destructive operation with permission nuances), no annotations, and no output schema, the description is reasonably complete. It covers the action, permissions, and audit log context, but lacks details on return values or error cases, which would enhance completeness for a deletion tool.

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 33% (only 'reason' has a description), and the description does not add meaning for the undocumented parameters 'channel_id' and 'message_id'. It implies the 'reason' parameter's purpose (audit log) but does not elaborate beyond what the schema provides. With low coverage, the description compensates minimally, meeting the baseline for partial parameter information.

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 ('Delete a single message') and resource ('message'), distinguishing it from sibling tools like 'discord_bulk_delete_messages' (which handles multiple messages) and 'discord_edit_message' (which modifies rather than deletes). The verb 'Delete' is precise and unambiguous.

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 clear context for when to use this tool by specifying permission requirements ('Requires Manage Messages for other users' messages; bot can always delete its own'), which helps differentiate it from alternatives like 'discord_bulk_delete_messages' for batch operations. However, it does not explicitly state when NOT to use it or name specific alternatives beyond implied distinctions.

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