pmg_tasks_list

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

No annotations are provided, so the description carries the burden. It correctly identifies the tool as read-only and lists key parameters and their behavior (pagination, filters). It does not describe side effects or error conditions but is sufficient for a read-only list tool.

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 concise and well-structured: it opens with the purpose and prerequisite, then provides technical context (API path) and parameter explanations in separate lines. No superfluous information.

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 has 10 parameters, 0 required, and an output schema exists, the description covers the essential parameters but leaves out since and until. The API path mention adds useful context. Mostly complete for a list operation.

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 only 10% schema description coverage, the tool description compensates by explaining start, limit, errors, and the text filters (userfilter, typefilter, statusfilter). However, it omits explanations for node, since, until, which are left to the schema's type info.

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 it lists PMG tasks on a node and is a read operation. However, it does not differentiate from sibling task list tools (e.g., pbs_tasks_list, pve_tasks_list) explicitly.

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 mentions a prerequisite (PROXIMO_PMG_* config) but does not provide guidance on when to use this tool vs alternatives or when not to use it.

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