pve_replication_create

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

No annotations provided, so description carries full burden. Discloses key behaviors: mutation, dry-run default, execution requirement (confirm=True). Does not detail dry-run effects or error handling, but adequate for a tool with simple execution flow.

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?

Two sentences, front-loaded with clear purpose and key information. No filler; every word adds value.

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?

Despite having an output schema, the description is too minimal. It omits explanation of replication jobs, required parameters (rep_id, target), and other parameters. For a tool with 9 parameters, the context is insufficient for correct invocation.

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?

Adds meaning for rep_type ('typically local') and confirm ('True to execute'), which the schema does not explain. However, with 11% schema description coverage and 9 parameters, most parameters (rate, rep_id, target, comment, disable, schedule) lack any description or usage hints.

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?

Clearly states mutation verb ('create'), resource ('PVE replication job'), and key behaviors (dry-run by default, how to execute with confirm=True). Distinguishes from siblings like pve_replication_delete and pve_replication_update by being the create variant.

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 explicit guidance: dry-run as default, confirm=True to execute, and typical rep_type value. Lacks explicit when-not-to-use or prerequisites, but context is clear for a create operation.

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