pve_replication_delete

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

With no annotations, the description fully discloses behavior: it's a mutation, dry-run default, synchronous execution (no task UPID), replication ceases, and data is NOT removed. No hidden behaviors or contradictions.

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?

Four succinct sentences, each providing critical information. The first sentence immediately states the action. No filler, every sentence earns its place.

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?

Covers all key aspects: mutation type, dry-run mechanism, execution gate, return behavior, and data retention. Output schema supplements return details. No gaps given the tool's simplicity.

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%. The description adds behavioral context for 'confirm' (dry-run vs execute) and implies rep_id usage. While it doesn't elaborate on proximo_target, the schema already documents it fully. Thus, description adds marginal value beyond 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 explicitly states 'delete a PVE replication job' – a specific verb and resource. It also clarifies key nuances: data is not removed, and the operation has no undo, distinguishing it from creation tools like pve_replication_create.

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?

Provides clear guidance: dry-run by default, use confirm=True to execute, and mentions no undo (re-create with pve_replication_create). Lacks explicit when-not-to-use or comparisons to other deletion tools, but the context is sufficient for correct invocation.

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