backup_job_list

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

Discloses return format including truncated flag and the list structure. With no annotations, the description carries the full burden. It gives a good sense of behavior as a read operation with pagination semantics.

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?

Very concise: two paragraphs with key purpose, return structure, and parameters. Every sentence adds value and the structure is front-loaded with purpose.

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?

For a list tool with two optional parameters and no output schema, the description fully explains return format, pagination via truncated flag, and parameter defaults. No missing pieces.

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?

Despite 0% schema description coverage, the 'Args:' section explains 'limit' (default 200) and 'target' (Xen Orchestra target name). This adds meaning beyond the bare 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?

Description explicitly states 'List VM backup jobs (id, name, mode)' with a clear verb and resource. It distinguishes from siblings like backup_log_list and backup_failure_rca via the word 'jobs' and the initial '[READ]' tag.

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?

Provides clear context on use (list backup jobs) with default limit and target parameter guidance. Does not explicitly mention alternatives or when not to use, but the sibling tools cover distinct concerns.

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