sr_usage_rca

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

No annotations provided, so description bears full burden. It explicitly tags as [READ], and describes the three analysis actions (ranking, flagging, totalling). No contradictions, but could mention that it does not modify anything.

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?

Concise, front-loaded summary, uses bullet points for the three analysis actions. Every sentence is informative with no waste.

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?

No output schema, but description adequately outlines what the tool returns: cause+action per finding, rankings, overcommit flag, orphan totals. Sufficient for the tool's complexity.

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?

Only one parameter 'target' with no schema description (0% coverage). Description adds meaning: 'Xen Orchestra target name from config; omit for the default.' This clarifies its purpose and default behavior beyond the schema.

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 does 'SR usage root-cause analysis' with cause and action per finding. Distinct from sibling tools like sr_list or sr_get by focusing on RCA, not just listing or reading SRs.

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?

Gives a hint about 'target' parameter default but no explicit guidance on when to use this tool instead of others like sr_list, sr_get, or other RCA tools. Implicit usage is for analyzing SR storage issues.

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