pve_users_list

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

No annotations are provided, so the description carries the full burden. It declares the operation is read-only and states the scope 'across every realm'. It also lists the specific fields returned. This is sufficient transparency for a list operation, though it could mention if there are any limitations like pagination or filtering.

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: first sentence covers purpose, scope, and read-only nature; second sentence lists return fields and points to sibling. Highly efficient, no wasted words, and front-loaded.

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 is simple (list all users), has an output schema (so return values are documented), and the description covers purpose, scope, and alternative tool, it is complete. No gaps identified.

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 description coverage is 100%, and the schema already fully describes the 'proximo_target' parameter with detailed explanation. The description does not add extra parameter semantics beyond the schema, so 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 uses specific verb 'List' and resource 'all Proxmox users across every realm', clearly stating it's read-only. It also lists the returned fields, distinguishing it from sibling 'pve_user_get'.

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 mentions 'Use pve_user_get for one user's full config, tokens, and effective ACL', providing a clear alternative for detailed single-user info. It implicitly guides when to use this tool (when you need a broad list of users) vs. when to use the sibling. However, it does not explicitly state when not to use this tool.

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