pve_backup_job_delete

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

No annotations provided, so description carries full burden. It discloses dry-run behavior, mutation type, and non-deletion of backups. However, it does not mention auth requirements, reversibility, or error handling.

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?

Extremely concise: two sentences, no filler. Front-loaded with 'MUTATION:' to indicate write operation. Efficiently conveys key 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?

Given the existence of an output schema, the description does not need to explain return values. It covers the operation, safety net (dry-run), and outcome. Could hint at error scenarios, but sufficient for a deletion tool.

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?

With only 33% schema coverage, description adds value by explaining the `confirm` parameter (default dry-run). For `job_id`, it relies on schema name. `proximo_target` is already described in schema. Adequate but not comprehensive.

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 clearly states the action (delete) and resource (PVE cluster backup job), and distinguishes from sibling tools like pve_backup_delete by specifying that existing backups are NOT deleted.

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?

Describes the dry-run default and that confirm=True is required for execution. Explains the effect on schedule and backups. Could explicitly mention alternatives (e.g., pve_backup_delete for backup files) but overall provides clear usage context.

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