discord_delete_sticker

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

Annotations already flag destructiveHint and non-idempotency, but the description adds substance beyond them: the deletion is irreversible, artwork is gone, and messages that used the sticker lose the image. It also discloses the permission gate and the return value, which annotations cannot express.

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?

Four compact sentences, with the irreversible warning front-loaded ahead of prerequisites and edge cases. No sentence is filler; each adds a distinct operational fact.

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?

An output schema exists, so the brief mention of the return value is a bonus rather than a necessity. Combined with full schema coverage and annotations, the description leaves nothing an agent needs unresolved for a destructive single-resource delete.

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 guild_id, sticker_id, and reason are fully documented inline and the description adds no syntax or format detail beyond that. Baseline 3 is appropriate when the schema carries all parameter meaning.

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?

States a specific verb and resource (delete a custom sticker from the server) and immediately scopes it: guild stickers only, not Discord-provided standard stickers. That scope distinction separates it cleanly from siblings like discord_edit_sticker and discord_delete_emoji.

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?

Gives a clear negative condition (standard stickers cannot be deleted) and a prerequisite (Requires Manage Expressions), which is real usage context. It stops short of explicitly routing an agent to an alternative sibling, so it lands just below the top.

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