Apply Discord Backup Restore

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

Annotations already declare destructive and non-idempotent, but the description adds real behavioral context beyond them: a pre-restore backup is created first, expectedPlanHash mismatches are rejected before mutation, and deletes require includeDeletes: true. It stops short of covering confirm gating or allowCrossGuild behavior, so not a 5.

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?

A single dense sentence, front-loaded with the core action and followed by safety-critical clauses in priority order. No filler sentences; each clause (pre-backup, hash gate, delete opt-in) carries distinct information.

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?

An output schema exists, so return values need not be explained, and the destructive-safety narrative is well covered. Gaps remain for a 7-parameter mutating tool: confirm, allowCrossGuild, and the required identity parameters are undocumented, and the source of expectedPlanHash (the plan tool) is not named.

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 0%, so the description must carry parameter meaning. It clarifies only two of seven parameters (expectedPlanHash's mismatch behavior and includeDeletes gating deletes); the required backupId/targetGuildId and the confirm, reason, and allowCrossGuild parameters get no explanation anywhere.

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: 'apply role/channel create/update operations from a backup,' which distinguishes it as the execution step of the backup family. It does not explicitly name the sibling it complements (discord_backup_restore_plan) or contrast with discord_backup_diff/read, so operational differentiation is left partly 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?

Usage is implied through the expectedPlanHash gate and the pre-restore backup, suggesting a plan-then-apply workflow. However, the description never explicitly says to run discord_backup_restore_plan first or when to prefer apply over other restore-related siblings, leaving the routing to inference.

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