cluster_create

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

Annotations indicate readOnlyHint=false (consistent with write operation) and openWorldHint=true. The description adds behavioral context like default values and optional configurations, which aligns with annotations. No contradictions.

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?

The description is a single paragraph with a clear, front-loaded purpose and a bulleted parameter list. Every sentence adds value, and there is no unnecessary wording.

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 6 parameters (1 required) and the presence of an output schema (not shown), the description covers creation aspects well. It could mention prerequisites like vCenter permissions or potential time delays, but overall it is sufficiently complete for a creation tool.

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 description coverage is 0%, so the description must compensate. It provides full parameter meanings: name (required), datacenter (uses first if omitted), ha/drs (default False), drs_behavior (lists three valid values), and target (optional). This goes well beyond the schema's basic type definitions.

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 '[WRITE] Create a new cluster with optional HA and DRS configuration,' which clearly identifies the verb (Create), resource (cluster), and scope (with optional HA/DRS). It distinguishes from sibling tools like cluster_configure (modify) or cluster_delete (remove).

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?

The description provides clear context: it's for creating a cluster, with defaults like first datacenter if omitted and False for ha/drs. While it doesn't explicitly list when not to use or name alternatives, the purpose is distinct enough to guide selection.

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