overview

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

Annotations are absent, so description carries full burden. Discloses best-effort execution and error block behavior, adding important behavioral context beyond the schema. Also indicates read-only nature with '[READ]'.

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 concise with a header and brief explanation. Every sentence adds value. Could be slightly more structured, but it's efficient and front-loaded.

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 complexity of fanning out into multiple collections and no output schema, the description lacks detail on the return structure. It summarizes what is covered but doesn't specify the output format, which may reduce completeness for an agent.

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 schema coverage 0%. Description explains it as 'Xen Orchestra target name from config; omit for the default', providing meaning and usage guidance beyond the schema minimal 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 clearly states verb '[READ]' and resource 'health summary' covering specific entities (pools, hosts, VMs, SRs, recent backups). It distinguishes from sibling read ops by being a one-shot aggregator that fans out, providing a clear starting point for triage.

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 'Start any triage here' and explains it fans out over other read ops, indicating when to use. Mentions best-effort behavior and error handling. No explicit exclusions or alternatives listed, but context is clear enough.

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