Plan Discord Backup Restore

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

Annotations already state readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description reinforces non-mutation while adding that the plan compares live state and includes a stable planHash. It does not add permission, rate-limit, or scope details beyond what annotations already cover.

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?

It is a single front-loaded sentence with no waste, stating the action, safety property, comparison behavior, and a key output field.

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?

With rich annotations, complete parameter descriptions, and an output schema, the description is sufficient for correct invocation and clarifies the non-mutating planHash output. The only meaningful gap is the lack of explicit sibling routing guidance.

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%, so both required parameters are already documented. The description reinforces that backupId refers to the stored backup and targetGuildId to the live guild, but adds no format or validation detail 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 gives a specific verb and resource: create a non-mutating restore plan comparing live guild to stored backup, and includes a stable planHash. This clearly distinguishes it from the mutating restore-apply sibling, though it does not explicitly name any sibling.

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 phrase 'non-mutating restore plan' implies previewing before applying, but the description never explicitly says when to use this versus discord_backup_diff or discord_backup_restore_apply. Usage is inferable but not stated.

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