delete_backup

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

Annotations already declare destructiveHint=true, and the description adds the access requirement 'backup and destructive access,' which is not covered by annotations. This provides useful context about required permissions beyond what the annotations state, though it does not elaborate on consequences or reversibility.

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?

The description is exceptionally concise: two short sentences that front-load the purpose and add a requirement. There is no wasted verbiage, and the structure is clear and efficient.

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?

The description covers the core operation but is incomplete given the optional server_id parameter and lack of return/error behavior. No output schema exists, and annotations don't fill the gap for parameter semantics. It is minimally adequate but leaves room for ambiguity in multi-server scenarios.

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%, and the description provides no information about backup_id or server_id. The tool's parameters are not explained, leaving the agent to infer their meaning solely from names. The optional server_id's purpose or when to use it is entirely undocumented.

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 'Delete a backup' uses a specific verb and resource, clearly distinguishing it from sibling tools like create_backup, list_backups, and deploy_backup. It is unambiguous and directly states the tool's action.

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 description mentions the requirement for 'backup and destructive access,' implying a prerequisite for use, but it does not provide explicit when-to-use guidance or alternatives. Usage is implied from the tool's name and purpose, but no contrasting tools are mentioned.

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