pdm_acl_list

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

With no annotations, the description carries full burden. It implies a read operation ('list') but does not explicitly state it's non-destructive, nor does it mention authorization needs beyond the config hint. Missing details on rate limits, side effects, or response behavior.

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 concise, front-loading the purpose with 'DIAGNOSE (LOW): list PDM access control entries.' It then lists parameters briefly. No wasted sentences, though the 'DIAGNOSE' prefix could be considered slightly extraneous.

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 output schema exists, the description doesn't need to explain return values. It covers parameters and a configuration prerequisite. However, it doesn't clarify the scope of the listing (all entries? filtered by path?), which is important 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?

The description adds meaning for 'path' and 'exact' parameters beyond the schema (providing example and behavior). The third parameter 'proximo_target' is well-described in the schema itself, so the description's omission is acceptable. Overall adds value to understanding parameter usage.

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 action ('list PDM access control entries') and the resource ('PDM ACL entries'). It distinguishes from siblings by specifying 'PDM' context, though it doesn't explicitly name alternatives like pve_acl_list.

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?

It mentions optional path filter and exact flag, and notes the prerequisite 'Needs PROXIMO_PDM_* config', but lacks explicit guidance on when to use this tool versus alternatives (e.g., pve_acl_list) or when not to use it.

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