pdm_remotes_list

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

With no annotations, the description fully discloses that the operation is read-only, causes no state change, returns a list of remote dicts with credential-shaped keys stripped. It doesn't cover edge cases like empty results or error handling, but for a simple list tool this is sufficient.

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, using three short sentences with no filler. It front-loads the read-only nature and purpose, then adds behavioral details and alternatives efficiently.

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 parameter, no enums, list output with schema), the description covers all necessary context: purpose, safety, return value structure, and alternative tools. No gaps remain.

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%, so baseline is 3. The description does not add any extra meaning to the single parameter (proximo_target) beyond what the schema already provides, so it meets but does not exceed the baseline.

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 tool lists all PVE/PBS remotes registered in PDM, explicitly labeling it as READ-ONLY. It distinguishes from sibling tools by pointing to pdm_remote_version and pdm_remote_config_get for single-remote queries, leaving no ambiguity about its scope.

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 states when to use (listing all remotes) and when not to (for a single remote's version/config, use alternative tools). It also mentions the prerequisite configuration requirement (PROXIMO_PDM_*), providing clear usage context.

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