pve_list_replication_jobs

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

No annotations are provided, so the description carries the full burden. It states a read operation ('List'), implying it's non-destructive, but doesn't disclose behavioral traits such as permission requirements, rate limits, output format (e.g., list of objects with IDs), or pagination. This leaves significant gaps for an agent to use it effectively.

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 extremely concise with just three words, front-loading the core purpose without any wasted text. It's appropriately sized for a simple list operation with no parameters.

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 complexity (a list operation in a system with many sibling tools), no annotations, and no output schema, the description is incomplete. It doesn't explain what a replication job entails, the return structure, or how it fits into the broader Proxmox VE context, leaving the agent with insufficient information for reliable use.

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 input schema has 0 parameters with 100% description coverage, so no parameter documentation is needed. The description doesn't add parameter information, which is acceptable here. A baseline of 4 is applied as it appropriately handles the lack of parameters without redundancy.

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 'List replication jobs' clearly states the action (list) and resource (replication jobs), which is adequate for basic understanding. However, it lacks specificity about scope (e.g., all jobs, filtered by node/storage) and doesn't differentiate from sibling tools like 'pve_get_replication_job' (which likely retrieves a single job), making it vague in context.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention if this is for browsing all jobs versus using 'pve_get_replication_job' for details on a specific job, or if there are prerequisites like node access. The description offers no usage context.

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