pve_get_replication_job

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 this is a 'Get' operation, implying it's read-only, but doesn't disclose behavioral traits such as authentication requirements, error handling (e.g., if the ID is invalid), rate limits, or what the output looks like (since there's no output schema).

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, efficient sentence with zero waste. It's appropriately sized for a simple tool and front-loaded with the core action, making it easy to parse quickly.

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 tool's low complexity (one parameter) but lack of annotations and output schema, the description is incomplete. It doesn't provide enough context for an agent to understand the full behavior, such as what data is returned or potential side effects, leaving significant gaps despite the simple input.

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 100%, with the single parameter 'id' documented as 'Replication job ID'. The description adds no additional meaning beyond this, as it doesn't explain format, sourcing, or constraints. With high schema coverage, the baseline is 3, reflecting adequate but minimal value added.

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 'Get replication job configuration' clearly states the verb ('Get') and resource ('replication job configuration'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'pve_get_backup_job' or 'pve_list_replication_jobs' beyond the obvious resource difference, and it lacks specificity about what 'configuration' entails.

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. The description doesn't mention prerequisites (e.g., needing a job ID), exclusions, or comparisons to sibling tools like 'pve_list_replication_jobs' for listing all jobs versus getting a specific one's details.

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