List backup schedule jobs

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds 'cluster-wide' scope and 'scheduled' qualifier, but no additional behavioral traits like authentication needs, rate limits, or pagination. Adds some value beyond 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?

Single sentence of 5 words, zero waste, front-loaded information. Maximally concise while being informative.

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 tool with no parameters, no output schema, and comprehensive annotations, the description is adequate. It specifies what is listed and the scope. Could mention read-only nature, but annotations already cover that.

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?

No parameters in input schema (100% coverage). Description adds no parameter info, which is appropriate. Without parameters, baseline is 4.

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 it lists all scheduled vzdump backup jobs cluster-wide, using specific verb and resource. Distinguishes from siblings like list_backups and list_jobs by specifying 'scheduled vzdump backup jobs' and 'cluster-wide'.

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?

Clear context provided (scheduled backup jobs, cluster-wide), but no explicit guidance on when to use this tool versus list_jobs or list_backups. Implied usage is adequate, but direct exclusion of alternatives would improve clarity.

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