proxmox_node_service

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

Description mentions elevated permissions for control actions, which adds transparency beyond the schema. However, it does not disclose other behavioral traits like side effects or error handling, and annotations 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?

Two sentences with no extraneous information. The structure is compact and front-loads the core functionality.

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?

For a simple tool, the description covers main functionality but lacks detail on conditional requirements (e.g., service and command needed for control) and return values. Without output schema or annotations, more completeness would be beneficial.

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?

Description adds meaning for the 'action' parameter by explaining its values (list/control) and the elevated requirement for control. Schema covers 75% of parameters with descriptions, and the description compensates for the missing action description.

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?

Description clearly states the tool manages node services and specifies two actions (list and control) with distinct purposes. It distinguishes from sibling tools like proxmox_node by focusing specifically on services.

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?

Description explains when to use each action (list vs control) and notes elevated permissions for control. While it doesn't explicitly exclude alternatives, the specificity provides clear usage context.

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