get_node_version

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

No annotations are provided, and the description only states it gets version information. It does not disclose any behavioral traits (e.g., read-only nature, potential errors, or authorization needs), leaving the agent with insufficient safety context.

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 very short and to the point, with no wasted words. However, its brevity leads to omissions in other dimensions.

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 number of sibling tools (especially get_version and other get_node_* tools), the description lacks context about how this tool fits in. It does not explain the relationship to get_version or what 'version information' entails, though an output schema exists.

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?

With 0% schema description coverage, the description adds only the label 'node name,' which is minimally helpful. Baseline is 4, but the description does not provide format, examples, or constraints, so it adds limited value.

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 specifies 'Get Proxmox VE version information for a specific node,' using a clear verb and resource. It distinguishes from siblings like 'get_version' (global version) and other get_node_* tools.

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 implies usage requires a node name but does not explicitly state when to use this tool versus alternatives (e.g., get_version for global info). No prerequisites or exclusions are mentioned.

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