proxmox_cluster_config

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only hints at elevated privileges for 'join' but does not indicate whether other actions are read-only, destructive, or have side effects. Critical traits like idempotency or rate limits are absent.

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 front-loaded with the primary purpose, followed by a compact action list. It is efficient but somewhat dense due to pipe separators. No unnecessary words, but a slightly more structured format (e.g., bullet points) could improve readability.

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?

The description lacks information about return values or output format, which is important since no output schema exists. However, given the simplicity of the actions (get, list, join, totem), the missing details are somewhat tolerable. An agent would need to infer response structure from the action names.

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 high (83% as given), so the schema itself explains most parameters. The description adds value by listing action enum values in plain text, but no further parameter context is provided. Baseline 3 is appropriate.

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 clearly states 'Manage cluster config' and enumerates five specific actions via the action parameter, making the purpose distinct. However, it does not explicitly differentiate from sibling tool 'proxmox_cluster', which may cause confusion, hence not a 5.

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 'proxmox_cluster' or other config tools. The description lists actions but does not explain use cases or prerequisites, leaving the agent without contextual selection criteria.

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