templates_delete

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

The description goes well beyond the annotations by specifying the permission requirement, the non-effect on existing guilds, the exact return object, and the security gating via `__confirm:true` and `MCP_DRY_RUN=false`. This provides crucial behavioral disclosure for a destructive operation.

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 composed of four short, labeled sections (Purpose, Requires, Returns, Security), each containing essential information. There is no redundant or filler text, making it highly efficient and well-structured.

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 tool, the description covers purpose, required permissions, irreversibility, return value, and security confirmation flow. With an output schema present and annotations already indicating destructiveness, the description provides all necessary contextual information for an agent to use the tool safely.

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 schema already describes all four parameters with 100% coverage, providing a baseline of 3. The description adds explanatory context about the confirmation parameter (`__confirm:true`) and the MCP_DRY_RUN setting, which is not in the schema. It does not elaborate on audit_reason, but the schema covers it, so the extra value warrants a 4.

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 Template' with the clear verb 'Delete' and resource 'Guild Template', and emphasizes it is DESTRUCTIVE and IRREVERSIBLE, distinguishing it from sibling tools like templates_modify and templates_sync. This is a specific and unambiguous purpose.

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?

It clearly states the required Discord `MANAGE_GUILD` permission and clarifies that it only removes the template code, not existing guilds, which helps the agent understand the impact. It does not explicitly name alternatives or exclusion criteria, but the usage context is sufficiently clear.

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