pve_backup_freshness

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

No annotations exist, so the description bears full responsibility. It discloses read-only nature, that it walks actual archives (not trusting job reports), that unreadable storage yields unknown+complete=false, and lists possible verdicts. Lacks auth or rate limit details but covers key behavioral traits.

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?

Description is front-loaded with purpose and read-only tag, then explains behavior, verdicts, and return type. Efficiently mentions sibling differentiation. Slightly long but every sentence adds value.

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?

Output schema exists, so return value details are somewhat redundant. Description covers edge cases (unreadable storage) and behavioral nuances. For a read-only diagnostic tool, it provides sufficient context for safe invocation.

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 100%—all three parameters have descriptions. Description does not expand on parameter semantics beyond what the schema already provides, such as clarifying grace_hours or max_age_hours usage. Baseline 3 is appropriate.

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?

Description clearly states this is a read-only tool that checks backup freshness by walking actual archives. It lists possible verdicts and distinguishes itself from sibling tools pve_backup_list and pve_backup_job_list, providing a specific verb-resource combination.

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?

Description explicitly contrasts with pve_backup_list (raw archive list) and pve_backup_job_list (job configuration), helping the agent choose among siblings. It implies usage for verifying backup freshness but does not explicitly state when not to use it.

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