overview

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

Discloses read-only nature via [READ] tag, best-effort execution, and that failing collections return error blocks without blanking the rest. No annotations provided, so description carries full burden; it is sufficient.

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 brief yet complete, with purpose front-loaded in first line, usage guidance in second, and parameter info in a clean Args block. No unnecessary words.

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?

Given the tool's role as a summary, description covers scope, error behavior, and parameter. No output schema exists, but return structure is implied. Could mention more about what the summary contains, but adequate for triage start.

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?

Schema has 0% description coverage, but description adds meaning for the single parameter: 'Xen Orchestra target name from config; omit for the default.' This effectively compensates for the lack of schema doc.

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's a READ operation providing a one-shot health summary of pools, hosts, VMs, SRs, and recent backups. It distinguishes from siblings by noting it fans out over other read ops.

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?

Explicitly says to 'Start any triage here', indicating primary use case. Mentions best-effort behavior and error handling but does not specify when not to use or list alternatives beyond sibling context.

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