Start VMware Instant Recovery (destructive/impactful)

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

No annotations provided; description says 'Impactful — it publishes a running VM' which implies side effect but doesn't detail destruction or reversibility. Adequate but not fully transparent.

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?

Three sentences with no waste. Purpose first, then impact, then parameter guidance. Front-loaded and well-structured.

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?

For a mutation tool with no output schema, description covers purpose, parameters, and alternative method. Could mention response type, but functional completeness is high.

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 coverage is 100%, but description adds detail to restoreSpec parameter by listing typical fields (target host, datastore, etc.), helping agent understand expected JSON structure.

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?

Clearly states 'Launch Instant Recovery of a VMware VM directly from a backup restore point' with specific verb and resource. Distinguishes from sibling veeam_api_request by noting schema differences.

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?

Provides explicit context: when to use this tool vs veeam_api_request (if field names differ). Warns about impact. Lacks explicit 'when not to use' but gives clear instructions.

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