get_vm_spiceproxy

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

No annotations provided. The description claims 'Create' but the name suggests 'get', which is an internal inconsistency. It does not disclose whether the tool creates a temporary proxy or retrieves an existing one, nor does it explain side effects or authentication needs.

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 (two sentences) and front-loaded with the purpose. However, the first sentence is misleading due to the verb contradiction. Conciseness is achieved but at the expense of clarity.

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?

Even though an output schema exists, the description does not explain what the tool returns or how the proxy connection is used. Missing context about SPICE protocol, lifetime of the proxy, and relation to other console tools.

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?

Input schema has 0% description coverage. The description only repeats parameter names 'node' and 'vmid' without adding any meaning (e.g., valid ranges, format, or relationship to the proxy).

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 says 'Create a SPICE proxy connection' but the tool name starts with 'get', implying retrieval. The verb 'Create' contradicts the name, causing confusion. Also, there is a sibling tool 'get_vm_vncproxy' with similar purpose, but the description does not differentiate between SPICE and VNC.

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 on when to use this tool versus alternatives like 'get_vm_vncproxy'. The description does not specify the context for SPICE proxy usage or mention any prerequisites.

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