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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real context about what the call yields — per-backup run time, success flag, size, and storage location — which is exactly the kind of content annotations can't express. No pagination or volume limits are mentioned.

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?

Two sentences, zero waste: sentence one defines scope and return contents, sentence two lists the triggering scenarios. Front-loaded and appropriately sized.

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?

With no output schema, the description valuably enumerates returned fields (timing, success, size, storage location), covering what an agent needs to interpret results. There's no mention of how many recent archives are returned or whether large result sets are truncated, a minor gap for a list tool.

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% with a single required 'host' parameter fully described as 'Server id or exact name from hosts_list'. The description adds no syntax or format guidance beyond the schema, so baseline 3 applies.

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?

States a specific verb+resource: backup jobs and recent archives for one server, plus the fields returned (run time, success, size, storage location). It doesn't explicitly distinguish itself from sibling job_list or backup_create, which is the only thing keeping it from a 5.

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?

Gives two concrete situations: verifying a backup exists before a risky change and checking whether last night's backup succeeded. That's clear usage context, but it offers no exclusions or explicit pointer to siblings like job_status or backup_create.

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