delete_backup

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

Annotations already flag destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds real value beyond that by stating permanence and the two required environment gates (WISP_ALLOW_BACKUPS, WISP_ALLOW_DESTRUCTIVE), which pre-empt predictable auth failures. It does not say whether dependent artifacts or backups are affected.

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?

Two short sentences with the action and its irrevocability front-loaded, followed by the usage restriction and prerequisites. Nothing is redundant and nothing important is buried.

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 destructive mutation with full annotation coverage, full schema coverage, and no output schema, the definition supplies action, restriction, and prerequisites. The remaining gap is downstream effect - whether deleting a backup removes associated download artifacts or leaves the server in a locked state - which is not addressed.

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%, with backup_id documented as coming from list_backups and server_id documented as defaulting to WISP_SERVER_ID. The description adds only 'by ID', so the schema is doing all the parameter work and 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 ('Permanently delete a backup') plus the selector ('by ID'), which clearly separates it from list_backups, create_backup, and deploy_backup. It stops short of explicitly naming sibling tools, so an agent must infer the distinction, keeping it at 4 rather than 5.

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?

'Use only for an explicit backup deletion request' is a genuine when-to-use restriction that discourages speculative or bulk cleanup calls. It gives no named alternative for the adjacent cases (locking, archiving, redeploying), so the guidance is clear but not exhaustive.

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