proxmox_node_task

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

No annotations are provided, so the description must fully disclose behavior. It correctly indicates a query operation (read-only), but fails to mention that the 'get' action requires the 'upid' parameter, which is not declared as required in the schema. This omission could lead to errors.

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 a single sentence with a clear separator (pipe) for the two actions. It is front-loaded with the core purpose and wastes no words.

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 query tool with 3 parameters and no output schema, the description is mostly adequate. However, the missing requirement for 'upid' in the 'get' action is a significant gap. It also does not specify what 'recent' means or how results are paginated/ordered.

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?

The schema covers 67% of parameters (node and upid have descriptions). The description adds value by explaining the 'action' enum values ('list' vs 'get'), which the schema omits. However, it does not elaborate on 'node' or 'upid' beyond the schema.

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 'Query node tasks' and distinguishes two actions: 'list recent tasks' and 'get task details by UPID'. This provides a specific verb-resource pair and differentiates from sibling tools which cover other Proxmox domains.

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 outlines two actions but does not provide guidance on when to use this tool versus alternatives (e.g., proxmox_node_log or proxmox_guest_status). It lacks any context on prerequisites or common use cases, so the guidance is minimal but not misleading.

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