pve_api_request

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

With no annotations, the description carries the full behavioral burden. It does disclose one meaningful trait beyond the schema: mutating methods are gated behind confirm=true, implying GET is the safe default. However, it does not address PATCH, how confirm guards operations, serialization of params, or error/failure behavior — notable gaps for a tool that can reach arbitrary destructive endpoints.

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?

Two short sentences, no filler, and the core purpose is front-loaded before the constraint. Every sentence earns its place. It is slightly terse for the complexity of a generic passthrough tool, but as pure economy of language it is well-structured.

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?

An output schema covers return values, but this is an open-ended tool that can hit any Proxmox endpoint — the highest-complexity case in the sibling set. The description omits essential operational details: how params map to the request, how paths should be formatted, whether specific siblings should be preferred, and what happens on non-2xx responses. One sentence is insufficient for a tool of this scope.

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 0%, so the description must compensate. It partially does: it explains the method parameter (GET/POST/PUT/DELETE) and the confirm parameter (required for mutations). But path format (leading slash? full URL?) and params encoding (query string vs request body?) are left entirely undefined — two of the four parameters get no semantic help.

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 states a clear verb-resource pair: 'Call any Proxmox API path.' The word 'any' signals this is the generic passthrough/escape-hatch tool, implicitly distinguishing it from the 27 sibling tools that each target a specific operation. It is clear but could more explicitly position itself as the fallback for operations no dedicated tool covers.

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 provides a method-level rule (GET allowed, POST/PUT/DELETE need confirm=true) but gives no when-to-use guidance versus the specific sibling tools. For an escape-hatch tool, the key guidance would be 'use this only when no dedicated pve_* tool applies' — that is absent. The confirm rule is a how-to-use constraint, not a usage-selection guideline.

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