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

Annotations declare non-idempotent and destructive, and the description complements them with the key behavioral fact that 'The cluster will begin provisioning immediately after confirmation' and that required inputs are validated upfront. It stops short of describing failure modes, timeouts, or how long provisioning takes, but it clearly adds value beyond the annotation flags.

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?

Front-loaded with the core action, followed by prerequisites, preset naming, the discovery pointer, and the confirmation caveat. Four compact sentences with essentially no filler, though the preset-recap sentence is largely redundant with the schema.

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 22-parameter, no-output-schema, high-impact provisioning tool, the description supplies the prerequisites, the discovery path, the preset vocabulary, and the post-confirmation behavior. Annotations cover the safety profile, and the schema covers parameter detail, leaving nothing critical for the agent to guess before invoking.

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 100% across all 22 parameters, so the schema already documents every field thoroughly. The description's only parameter-relevant contribution is naming the t-shirt instance presets and the discovery tool, both of which are already reflected in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('Create and provision a new Kubernetes cluster on Proxmox VE'), so the agent immediately knows what is produced and on which platform. It does not, however, differentiate itself from the many sibling create_*_cluster/create_managed_cluster tools, so the agent must infer from the provider name alone.

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?

Gives clear prerequisites (Proxmox VE API credential, SSH key credential, host node, network bridge) and explicitly routes the agent to list_proxmox_options to discover nodes, presets, storages, bridges and templates. It does not state when to prefer this over sibling cluster-creation tools, but the context for calling it is well established.

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