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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds genuine context: it talks to the customer's Proxmox VE API and can take a few seconds, which is a latency warning an agent cannot get from the schema. It also discloses exactly which data sets come back in each mode. A fuller note on failure behavior or pagination would push this to a 5.

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 list contents before the workflow instruction, and every clause carries information (scoping, sequencing, latency). It is dense but slightly long; a single tighter sentence could carry the same payload.

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?

With no output schema, the description must describe returns, and it does so concretely (nodes with capacity, named instance-type range, node-scoped storages/bridges/templates). Complete enough to call correctly, though it could be more explicit about the response shape or empty/failure cases.

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%, so both parameters are already documented, including that node is optional and enriches the reply. The description restates that same conditional behavior rather than adding syntax or format detail, so the schema is doing the heavy lifting and baseline 3 applies.

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 (list) and a precisely scoped resource (the provisioning options a Proxmox VE credential can reach), and enumerates the exact contents (nodes with CPU/memory, instance presets, storages, bridges, templates). This is easily distinguished from the near-name siblings list_morpheus_options and list_upcloud_options.

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?

Explicitly prescribes the workflow: call before create_proxmox_cluster, first without a node to pick one, then with the chosen node to pick storage, bridge, and template. The when-to-use and the sequencing of the two calls are stated, not inferred.

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