stickers_delete_guild_sticker

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

The description emphasizes 'DESTRUCTIVE - IRREVERSIBLE' and explains the exact confirmation mechanism (__confirm:true and MCP_DRY_RUN=false). This adds behavioral context beyond the destructiveHint annotation, including the dry-run behavior and irreversible consequences.

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 extremely concise, using bold headers and bullets to present purpose, usage, and return value in just three short lines. Every sentence contributes meaningful information without redundancy.

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?

The description covers purpose, usage, safety confirmation, and the return shape. Given the simple scope of the tool, the rich schema, and the explicit output mention, it is fully complete for an agent to select and invoke correctly. Permissions are not mentioned but are not necessary for understanding the operation.

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 input schema has 100% coverage with descriptions for all parameters. The description only mentions __confirm briefly without adding new semantic details about the other parameters (guild_id, sticker_id, audit_reason), so it simply meets the schema baseline.

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 states 'Delete a guild sticker' with a specific verb and resource, clearly distinguishing it from sibling sticker tools like stickers_modify_guild_sticker or stickers_create_guild_sticker. The destructive nature is also highlighted upfront.

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 a 'When to use' section with a concrete scenario ('Retire a stale or off-brand sticker'), giving clear context for when to invoke the tool. However, it does not explicitly mention alternatives or when not to use it, so it falls short of a 5.

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