sr_usage_rca

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

Clearly labels as [READ] and details analysis steps (ranking, flagging, totaling), providing transparency beyond default expectations without 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?

Two terse paragraphs; first conveys purpose and key actions, second documents parameter. No fluff, every sentence earns its place.

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?

Covers purpose, actions, and parameter adequately. Lacks explicit output format but given simple input, it is sufficiently complete for selection and invocation.

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?

Explains the 'target' parameter meaning (Xen Orchestra target name, optional) despite 0% schema coverage, adding value over the schema's anyOf definition.

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 states 'SR usage root-cause analysis' with specific actions (rank, flag, total), distinguishing it from sibling RCA tools like backup_failure_rca and vm_health_rca.

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?

Implies usage for analyzing SR storage issues but lacks explicit when-to-use vs alternatives or when-not-to-use guidance.

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