pve_replication_delete

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

Without annotations, the description fully discloses behavioral traits: it is a mutation, dry-run by default, requires confirm for actual execution, and importantly states that existing replicated data is NOT removed. This provides complete transparency.

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?

Three sentences with the key purpose front-loaded. Every sentence provides essential information: action, dry-run, confirm, and data safety. No wasted words.

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 presence of an output schema and the tool's complexity (simple delete with dry-run), the description covers purpose, usage, and behavioral outcomes. It could briefly mention the required rep_id parameter, but the schema covers it. Missing parameter guidance slightly reduces completeness.

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 only 33% (only proximo_target has a description). The tool description does not add any meaning for rep_id or confirm beyond their names, failing to compensate for the missing schema descriptions. The confirm parameter's role is implied but not explicitly detailed.

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 'delete a PVE replication job', using a specific verb and resource. The 'MUTATION' prefix and distinct resource name differentiate it from siblings like pve_replication_create and pve_replication_update.

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 explains the dry-run default behavior and how to execute with 'confirm=True'. It provides clear context on when to use the confirm parameter but does not explicitly state when not to use the tool or mention alternatives.

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