pve_backup_list

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

With no annotations provided, the description carries the full burden. It declares the tool is read-only and provides the key behavioral trait of being comprehensive across nodes and task windows. However, it omits details like permissions, pagination, or output size, making it adequate but not detailed.

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 two sentences with no extraneous words. It front-loads the action and read-only nature, then adds key context. Every sentence earns its place.

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?

The description is adequate for a simple list tool, especially with an output schema covering return values. However, it does not clarify the role of all three parameters nor differentiate from all relevant siblings (e.g., pve_storage_content, pve_backup_job_list). It provides a key distinction from pve_tasks_list but is not fully 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 description coverage is only 33% (only proximo_target described). The tool description does not explain the 'node' or 'storage' parameters, failing to compensate for the low coverage. The description adds no extra meaning beyond the schema for these parameters.

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 clearly states the verb and resource: 'List backup archives in a storage (read).' It distinguishes itself from pve_tasks_list by noting it is the 'ground truth for whether a backup exists,' which differentiates it from sibling tools.

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 explicitly contrasts this tool with pve_tasks_list, explaining that backups missing from that listing still appear here. This gives clear context on when to use this tool, though it does not explicitly mention when not to use it or list alternatives.

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