cluster_add_host

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

Description claims idempotent behavior, but annotations set idempotentHint to false. This is a direct contradiction. Other behavioral details are fine but the contradiction outweighs.

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 well-structured with sections, but slightly verbose. However, every sentence adds value. Could be tightened without losing clarity.

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, prerequisites, idempotency, comparison to siblings, parameters, and return values. Output schema exists but description still adds helpful return examples. Complete for a write tool with these constraints.

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?

Input schema has 0% description coverage, but description fully explains each parameter: cluster_name (destination, created with cluster_create), host_name (FQDN example), target (from config.yaml, optional). Adds crucial context beyond 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?

The description explicitly states the verb 'Move' and resource 'ESXi host into a cluster', and distinguishes from registering new hosts and from cluster_remove_host. It clearly differentiates itself among siblings.

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 when to use (move managed host into cluster), when not to use (first-time registration), alternatives (cluster_remove_host, cluster_info), and prerequisite (host already in vCenter inventory).

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