proxmox_cluster_replication_job

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

No annotations are provided. The description only notes 'elevated' for certain actions, but lacks details on side effects, idempotency, state changes, or error conditions. Behavioral transparency is minimal.

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 sentence with a list, which is concise. However, it could be more efficient by grouping 'elevated' once. It lacks structure for readability and depth.

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 14 parameters, no output schema, and missing behavioral details, the description is severely incomplete. It fails to provide necessary context for correct usage.

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%, and the description does not explain any of the 13 non-action parameters. The enumeration of actions is helpful but does not compensate for the lack of parameter semantics.

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 states 'Manage cluster replication jobs' and lists specific actions (list, get, create, update, delete), making the purpose clear. However, the verb 'Manage' is generic, and there is no explicit differentiation from sibling tools like proxmox_node_replication, though the cluster-level scope is implied.

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 mentions 'elevated' for create/update/delete, hinting at permission requirements, but provides no guidance on when to use this tool versus alternatives, no context on prerequisites, and no exclusions.

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