Cluster Replication Jobs

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the safety profile is clear. The description adds a minor behavioral note by marking create/update/delete as 'elevated', which is useful. However, it doesn't disclose side effects or edge cases (e.g., what happens on delete), so it only marginally exceeds the annotation baseline.

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 a single, terse sentence that front-loads the core purpose and then lists actions via pipes. It is efficient with no filler. However, it's dense and could benefit from line breaks or clearer grouping, but overall it's appropriately concise.

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 tool has 14 parameters, no output schema, and multiple actions, the description is severely under-specified. It doesn't explain which parameters are relevant for each action, what a replication job is, or how the 'elevated' flag affects invocation. An agent would struggle to construct correct calls without additional documentation. The description is far from complete for this complexity level.

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 21% (only 3 of 14 parameters have descriptions). The description provides zero parameter information—no mapping of actions to required parameters, no explanations of fields like 'source', 'target', 'schedule', or 'remove_job'. With such low schema coverage, the description should compensate, but it doesn't mention any parameters at all.

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 tool manages cluster replication jobs and enumerates five specific actions (list, get, create, update, delete). This is a specific verb-resource combination that distinguishes it from node-level replication tools. However, it doesn't explicitly contrast it with proxmox_node_replication or other cluster job tools, so it's not a full 5.

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?

There is no guidance on when to use this tool versus alternatives like proxmox_node_replication. The description only lists actions without any context about prerequisites, when to choose this over sibling tools, or what scenarios warrant each action. The '(elevated)' hints at permissions but not usage context.

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