proxmox_node_replication

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

No annotations exist, so description carries full burden. It mentions 'elevated' for schedule, but does not disclose other behavioral traits such as side effects, output format, or error conditions. Minimal transparency beyond basic action directives.

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?

Extremely concise: two short sentences that front-load purpose and action details. Every part is necessary and without waste.

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 no output schema and no annotations, the description is minimal but covers basic functionality for a simple 3-parameter tool. However, it lacks details on output, potential errors, and integration context with siblings, making it only modestly complete.

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 high (67% with descriptions for node and id, enum for action). Description adds context that 'schedule' action triggers now with elevated privileges, which goes beyond schema but is still limited. Baseline 3 is appropriate.

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 resource (node replication) and actions (status/log query, schedule trigger). While it distinguishes between query and trigger, it does not differentiate from sibling tools like proxmox_cluster_replication_job, leaving some ambiguity.

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?

Gives action options and notes elevated permissions for schedule, but no explicit guidance on when to use this tool versus alternatives. With many sibling tools, this is a notable gap.

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