discord_admin_messages

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds little beyond restating operations; it does not disclose side effects, rate limits, required permissions, or constraints (e.g., bulk-delete limits). No contradiction with annotations is present.

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 a single, perfectly concise sentence that front-loads the primary actions. Every word is functional, and no filler is present.

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 tool with multiple operations, five parameters, and no output schema, the description is too sparse. It omits return values, operation-specific input requirements, and behavioral constraints. The tool's complexity demands far more detail for an agent to invoke it correctly.

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 repeats operation names from the 'operation' enum but does not explain how parameters like data, messageId, channelId, or reason map to each operation. With only 40% schema description coverage, the description fails to compensate for the lack of parameter detail.

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 a set of operations ('Get, edit, delete, bulk-delete, pin, unpin, or list pinned messages') on the 'messages' resource. It is specific and largely distinguishes this tool from siblings like discord_read_messages by focusing on admin actions, though it does not explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus siblings such as discord_send_message or discord_read_messages. There is no mention of prerequisites, operation selection criteria, or exclusions (e.g., when bulk_delete is preferred over delete). The description is purely a list of capabilities.

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