pdm_resources_list

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

With no annotations, the description carries full burden. It clearly states 'READ-ONLY', 'No state change', and 'Returns a flat list of resource dicts'. This sufficiently discloses the read-only nature and output format. Missing details on pagination or edge cases, but overall strong.

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, front-loaded with 'READ-ONLY', no wasted words. Every sentence provides value: purpose, behavior, alternatives, and prerequisites. Perfect conciseness.

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's simplicity (one optional param, no nested objects, output schema exists), the description covers purpose, boundaries, and prerequisite (config). It lacks details on return structure beyond 'flat list of resource dicts', but that suffices for a list tool.

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% for the single parameter 'proximo_target', so the description adds little beyond stating 'across ALL PDM-registered remotes'. Baseline 3 is appropriate; no additional parametric insight is provided.

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' and the resource 'every fleet resource (VMs, LXCs, storage, etc.) across ALL PDM-registered remotes'. It effectively distinguishes from siblings like pdm_resources_status (counters) and pdm_pve_resources (single remote), earning a top score.

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 explicitly tells when to use alternatives: 'For counters instead of the full list, use pdm_resources_status; to scope to one remote, use pdm_pve_resources.' It also mentions the config requirement, providing clear guidance for selection.

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