Pin, unpin or delete a message (admin)

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety profile is partially covered. The description adds the consequence that deletion cannot be undone and a required confirmation step, plus the behavioral nuance that publish pushes a message to following servers. It omits permission requirements and pin-count limits, but the added value is real.

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 short sentences with zero filler. The action inventory comes first, and the irreversible-delete warning is placed where it will be noticed.

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 multi-action tool with no output schema, the description covers every action and the critical risk of deletion. It does not state what list_pins returns, what permissions each action needs, or limits on pinned messages, which leaves modest gaps.

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 coverage is 100%, so action, channel_id, message_id and reason are all documented in the schema, including the note that message_id is not needed for list_pins. The description adds no further meaning about parameter formats or interactions, so the baseline 3 applies.

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 specific verbs and names the resource: pin, unpin, list pins, publish, delete a message. It enumerates all five actions matching the enum, so an agent can map intent to action without opening the schema. It does not differentiate from siblings such as discord_admin_purge_messages or discord_edit_message, which keeps it from a 5.

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 gives one explicit situational rule: confirm with the user before deleting, since deletion is irreversible. It offers no guidance on when to use this versus purge_messages for bulk removal or edit_message for content changes, so routing between siblings is left to inference.

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