pdm_remotes_list

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

As a read-only list operation with no annotations, the description adequately conveys safety (listing) and a prerequisite (config). It does not disclose additional behavioral traits beyond the obvious read nature.

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 very short (two lines) and front-loaded with usage context. It is concise but could include a brief note on output or error conditions.

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 low complexity, an output schema exists, and the description covers the core operation and a key prerequisite. It is fairly complete but lacks details on potential errors or pagination.

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 clear parameter description in the schema. The tool description adds no extra parameter-level information beyond 'needs config', so baseline 3 applies.

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 'all PVE/PBS remotes registered in PDM'. It distinguishes from sibling tools like pbs_remotes_list by specifying the PDM context.

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 'DIAGNOSE (LOW)' prefix and 'Needs PROXIMO_PDM_* config' provide context for when to use this tool, but it does not explicitly compare with alternatives like pbs_remotes_list.

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