discord_architect_delete_structure

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

Goes well beyond destructiveHint=true: it discloses that message history is permanently lost, that deleted roles are stripped from every member, that a literal 'CONFIRM DELETE' is required or nothing is deleted, that deletions are sequential with per-entity failure reporting, and which Discord permissions are needed. This is the kind of consequence detail an agent needs before an irreversible mutation.

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?

Five tight sentences, front-loaded with the action and the irreversibility warning before mechanics and permissions. No filler; each sentence carries a distinct 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?

Covers consequences, gating, permissions, and failure behavior adequately for a destructive bulk operation, and an output schema exists so return values need not be described. The unexplained 'plan' mode, which has no corresponding parameter, is the one loose end.

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 the schema already documents guild_id, channel_ids, role_ids and the exact confirmation constant; the description mostly restates the confirmation behavior. It also references being 'driven by a plan', but no plan parameter exists in the schema, which adds ambiguity rather than 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 set (delete channels, categories and roles) plus the two input modes (plan-driven or explicit IDs), so the agent knows it is a bulk structural delete. It never names the single-entity siblings discord_delete_channel or discord_delete_role, so the boundary with those tools is left to inference.

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 implies when this tool is appropriate (bulk removal of structure, or applying a plan) and reveals the preview-vs-apply mechanism, but it gives no explicit exclusions or 'use X instead for a single channel/role' routing against discord_delete_channel, discord_delete_role, or discord_architect_apply.

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