backup_job_list

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

readOnlyHint=true already covers the safety profile, so the description earns credit for adding the fields beyond annotations: the return envelope (jobs/returned/limit/truncated) and the meaning of truncation, which is genuine operational context. It stops short of noting anything about ordering, cost, or auth, but it is materially richer than the annotations.

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?

Front-loaded with the [READ] tag and purpose, followed by return shape then args — a sensible order. The embedded return-shape JSON is justified because no output schema exists; wording is tight with no filler.

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 supplies the response envelope and truncation semantics, and documents both parameters. The only real gap is the absence of any routing guidance relative to the backup/log siblings, which the structured fields cannot provide.

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 0%, so the description must carry the burden and largely does: limit is defined as max jobs with its default, and target is explained as a Xen Orchestra config name with omit-for-default behavior. Both parameters are covered, though no format/validation detail for target is given.

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?

Specific verb + resource ("List VM backup jobs") plus the identity fields returned (id, name, mode). This is clearly distinguishable from the other backup siblings (backup_log_list, backup_failure_rca) by its resource alone, so an agent can select it without opening a schema.

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 when-to-use, when-not, or alternative is stated. Nothing tells the agent why it would pick this over backup_log_list or backup_failure_rca, nor what prerequisites (target config) are needed before calling. Usage is only inferable from the tool name.

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