get_vm_vncproxy

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

The description says 'Create a VNC proxy connection ticket', implying mutation, while the tool name starts with 'get', suggesting a read operation. This inconsistency is misleading. No annotations are provided, so the description fails to clarify the actual behavior (e.g., whether it creates a ticket or retrieves one).

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 front-loaded with the key purpose. The parameter listing is clear but could be integrated more naturally. Despite the verb-name mismatch, the structure is efficient with minimal wasted text.

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 tool modifies state (creates a ticket) and has no annotations, the description should explain preconditions, effects, and output. It does not mention return values, safety implications, or any prerequisites. The presence of an output schema does not excuse the lack of behavioral context here.

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 should add substantial meaning. However, it merely restates parameter titles (e.g., 'The node name', 'The VM ID') without additional context. Only 'Use WebSocket connection' provides some value. This is insufficient to compensate for the lack of schema descriptions.

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 that the tool creates a VNC proxy connection ticket for console access. However, the verb 'Create' contradicts the tool name 'get', causing potential confusion. Additionally, it does not distinguish itself from the sibling tool 'get_vm_spiceproxy' which likely serves a similar purpose.

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?

There is no guidance on when to use this tool versus alternatives like 'get_vm_spiceproxy'. The description does not mention any prerequisites, conditions, or exclusions, leaving the agent without context for proper selection.

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