Delete a backup

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

With no annotations provided, the description carries the full burden of behavioral disclosure and fails to meet it: it does not say the deletion is irreversible, whether backups must be unlocked first, what permissions/keys are required, or what happens on success. For an irreversible mutation this is a significant gap.

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 short sentence with the action front-loaded and no filler. It is efficient, though its brevity is under-specification rather than deliberate density.

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 destructive, unannotated tool with six parameters, 67% schema coverage, no output schema, and undescribed required identifiers, the description should explain permanence, prerequisites, and parameter meaning. None of that is present.

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 only 67%, and the two required parameters (server, backup) have no schema descriptions at all — the description likewise adds nothing about whether "backup" is a name, UUID, or index, or how it relates to the server. Only the panel/baseUrl/key overrides are documented, and only by 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 states a specific verb and resource ("Delete a backup"), which is clearer than the title alone, but it does nothing to distinguish this from siblings like backup_restore, backup_toggle_lock, or backup_get — the agent must infer that this is the destructive 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?

There is no guidance on when to use this versus backup_restore or backup_toggle_lock, no mention of prerequisites such as whether a locked backup must be unlocked first, and no exclusions. The agent gets an implied destructive intent from the name only.

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