create_cluster

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Create a new K3s cluster definition' without explaining side effects, idempotency, or whether it triggers any infrastructure changes. It does not even clarify if this is a local metadata operation or a remote API call, leaving major behavioral unknowns.

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 sentence with no waste, front-loading the core purpose immediately. It is appropriately concise for a simple create operation, though it sacrifices substance for brevity.

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 has 3 parameters, no output schema, no annotations, and multiple related siblings, the description is far too thin. It does not explain what 'definition' means in the context of K3s, what the user should expect after calling it, or whether it is a prerequisite for 'provision_cluster'. This creates a significant completeness gap.

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?

The input schema provides 100% coverage with descriptions for all three parameters (name, description, k3s_version), so the baseline is 3. The tool description adds no extra parameter semantics beyond what the schema already states, hence no uplift.

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 states a specific verb ('Create') and resource ('K3s cluster definition'), which clearly indicates the tool's function. However, it does not explicitly differentiate itself from sibling 'provision_cluster', leaving ambiguity about whether this creates a real cluster or just a definition. The word 'definition' provides a subtle hint but could be clearer.

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?

No guidance is provided on when to use this tool versus alternatives like 'provision_cluster' or 'list_clusters'. The description does not mention prerequisites, typical use cases, or exclusions, so the agent gets no help in selecting this tool.

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