Node Replication

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

The annotations are all false, so they do not reveal that status/log are read-only queries while schedule is a side-effectful trigger requiring elevation. The description adds exactly this action-specific behavioral context, which is valuable; the elevated note is somewhat vague but sufficient as a warning.

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 whole definition is one compact sentence with a front-loaded resource statement and a dense action mapping; there is no padding or redundant parameter repetition. The pipe notation is terse but readable and every phrase contributes.

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?

For a three-required-parameter tool with no output schema, the description covers action semantics and privilege context, which is sufficient for a basic call. However, it does not describe return values or outcomes for schedule, nor explicitly differentiate from cluster_replication_job, leaving some ambiguity for an agent.

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 67%: node and id are already described, but action has only an enum. The description compensates by explaining what each action value means and signaling that schedule is the privileged/mutating one. It adds meaning beyond the schema for the least-documented parameter.

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 names a concrete resource, node replication, and maps each action to its behavior (query vs. trigger), so an agent can see what the tool does beyond the generic title. It does not explicitly contrast with the sibling proxmox_cluster_replication_job, but the node-scoped name and action mapping make the purpose reasonably distinct.

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 'action=status|log: query | action=schedule: trigger now' gives clear conditional guidance at the action level and flags when elevated privileges are relevant. However, it never states when to prefer this tool over proxmox_cluster_replication_job or when not to use it, so alternative selection is left to inference.

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