backup_failure_rca

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

Declares [READ] clearly and describes classification behavior, but without annotations, it would benefit from explicitly stating it does not modify state.

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 somewhat concise but includes an Args section that redundantly lists parameters already in the schema, wasting space.

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?

Adequately describes output categories and sample messages; no output schema exists, so description sufficiently covers expectations.

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?

Provides clear, meaningful descriptions for both parameters (limit and target) beyond the schema, including defaults and usage hints.

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 it classifies failed/skipped backup runs by job and lists specific categories (vdi-chain, quiesce, etc.), clearly distinguishing it from sibling tools like backup_log_list.

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?

Implied usage via 'Classify failed / skipped backup runs' but does not explicitly state when to use this tool versus alternatives like backup_job_list or vm_health_rca.

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