discord_architect_delete_template

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

Goes well beyond the annotations: it names the required permission, spells out the real-world consequence of destruction ('the template code stops working immediately for anyone who has it'), and notes the confirmation return. That is exactly the extra context the destructiveHint=true flag cannot convey on its own, and nothing here contradicts the annotations.

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?

Three short sentences: action, precondition, consequence/return. The irreversibility warning is front-loaded after the action, and no sentence is filler.

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 two-parameter deletion tool with rich annotations and an output schema, the description covers the action, the permission gate, the blast radius, and the response shape. An agent has everything needed to decide and call correctly.

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 description coverage is 100% and both parameters (guild_id pattern, code) are documented in the schema. The description only reflects 'code' via 'by its code' and adds no format or constraint detail beyond the structured fields, so the baseline of 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?

States a specific verb and resource with the lookup key ('Delete a guild template by its code'), which is clearly distinct from the structure-manipulation siblings like discord_architect_delete_structure and from create/list template tools. It stops short of explicitly naming or contrasting any sibling, which keeps it out of the top band.

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?

'Requires Manage Server' gives a concrete precondition, but the description never says when to choose this over discord_architect_delete_structure or the other architect tools, nor when not to delete. Usage is only implied by the resource name.

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