pdm_roles_list

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

No annotations are provided, so the description must cover behavioral traits. It states it lists roles and privileges but does not mention that it is read-only, what permissions are needed, or any side effects. The presence of an output schema helps but does not substitute for behavioral disclosure.

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 two sentences that state the purpose and a key prerequisite. No wasted words; front-loaded with the action and resource.

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 simple nature of a list operation, the presence of an output schema, and high parameter coverage, the description covers the essential information. It is missing behavioral safety information but is otherwise complete for a diagnostic 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?

The schema covers the only parameter (proximo_target) with a full description. The tool description adds the prerequisite hint 'Needs PROXIMO_PDM_* config,' which indirectly relates to the parameter but does not directly add semantic meaning beyond the schema. Baseline 3 is appropriate.

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 all roles and their privileges in PDM, distinguishing it from similar tools like pve_roles_list (for PVE) and pdm_acl_list (for ACLs). The verb 'list' and resource 'roles and their privileges' are specific.

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 phrase 'DIAGNOSE (LOW)' suggests a diagnostic use case, and 'Needs PROXIMO_PDM_* config' indicates a prerequisite. However, it does not explicitly compare with alternative tools or state when to use this vs. other role/ACL listing tools.

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