pve_list_backups

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

Description adds substantial behavioral detail beyond readOnlyHint: lists applicable guest types (VM/CT), explains aggregation logic (scans all backup-capable storages), and specifies return format with field names and ordering.

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?

Well-structured with clear focus on purpose and behavior. Could be slightly more concise but front-loaded with essential information.

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?

Thoroughly covers all aspects: what the tool does, how it works, return fields, filtering options. Complete for a tool with only 2 optional parameters.

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 0%, but description explains purpose of both parameters (vmid filters to one guest, storage filters to one storage). Adds meaning beyond schema types.

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?

Clearly states 'List backup archives across storages' with optional filtering. Distinguishes from siblings like pve_storage_content by describing itself as a convenience wrapper that scans all backup-capable storages.

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?

Describes when to use (cross-storage listing, filterable by vmid/storage). Does not explicitly exclude alternatives but implies usage context. Sibling tools provide further differentiation.

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