pdm_resources_list

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

The description lacks behavioral details beyond the basic purpose. It uses 'DIAGNOSE (LOW)' hinting at severity but does not mention side effects, rate limits, or performance impacts. Without annotations, more transparency is expected.

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 extremely concise, with only two sentences, and front-loads the key purpose. No redundant information is present.

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 read-only diagnostic tool with one optional parameter and an output schema, the description covers the essential purpose and prerequisite. It is adequate for the task, though it could clarify the exact scope of 'fleet resources' and any limitations.

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 coverage is 100% with a detailed description of the one parameter (proximo_target). The description reinforces the config requirement but does not add semantic value beyond what the schema already provides.

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 the verb 'list', the resource 'all fleet resources (VMs, LXCs, storage, etc.)', and the scope 'across all remotes'. It distinguishes from sibling tools like pdm_pve_resources by emphasizing the cross-remoteness.

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 ('Needs PROXIMO_PDM_* config'), which provides some usage context, but it does not explicitly state when to use this tool over alternatives or provide exclusions. The guidance is implied by the tool's purpose but not directly stated.

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