pve_get_replication_jobs

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

No annotations exist, so the description carries the burden of behavioral disclosure. The verb 'List' implicitly indicates a read-only operation, but the description does not explicitly state safety, permissions, or any additional behavioral traits (e.g., scope, rate limits). It conveys the basic action but lacks richer transparency.

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 concise sentence that front-loads the main action ('List') and then provides a clear list of the output fields. There is no wasted wording or redundancy.

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 simple list operation with no parameters and an output schema, the description adequately covers the tool's purpose and content. It does not need to explain return values since an output schema exists. The description is complete enough for an agent to select this tool appropriately among siblings.

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?

The tool has zero parameters, so the baseline for parameter semantics is 4. The description does not need to explain any parameters since none exist, and the schema confirms this is complete (100% coverage with no properties).

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 uses the specific verb 'List' and clearly identifies the resource as 'VM replication jobs', which distinguishes it from sibling tools like pve_get_backup_jobs. The included fields (source, target, schedule, rate, status) further clarify the tool's exact purpose.

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 implies usage when a user needs to view replication jobs, but it does not explicitly state when to use this tool over alternatives or exclude other cases. No direct 'when' or 'when not' guidance is provided, so it falls at the 'implied usage' level.

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