soundboard_delete_guild_sound

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

Beyond annotations (destructiveHint=true), the description adds crucial behavioral details: it is 'IRREVERSIBLE', requires a confirmation flag and MCP_DRY_RUN=false to execute, and states the return shape. This significantly informs the agent about execution constraints and 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 succinct and well-structured with clear labels: Purpose, Returns, Security. Every sentence conveys essential information (what it does, output shape, execution gate), with no wasted words.

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 destructive action, the description covers the essential context: outcome (delete), irreversibility, confirmation gate, dry-run behavior, and response format. It does not mention needed permissions, but the annotations and schema offset that gap, making it sufficiently complete for safe invocation.

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 already provides 100% coverage with descriptions for all parameters, including the IRREVERSIBLE note on sound_id and the purpose of __confirm. The description adds only minor emphasis (e.g., 'DESTRUCTIVE') without new semantic meaning beyond the schema.

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 explicitly states 'Delete a guild soundboard sound', providing a specific verb and resource. It clearly distinguishes this from sibling tools like soundboard_modify_guild_sound or soundboard_get_guild_sound by focusing on deletion.

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 does not explicitly name alternatives or state when not to use this tool. While the destructive nature and confirmation requirement are clear, there is no guidance on e.g., using a modify operation for reversible changes. The purpose implies usage but lacks explicit exclusions.

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