pve_list_lxc

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

No annotations are provided, so the description carries the burden. The verb 'List' implies a read-only operation, and the description specifies output fields. However, it does not disclose potential edge behaviors like filter defaults, invalid node handling, or authentication requirements, offering only minimal behavioral context.

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 a single sentence with only 13 words, front-loaded with the action and resource. Every word is informative, and it avoids redundancy with the schema fields.

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?

For a simple list tool with two optional parameters, the description covers the core purpose and output fields. It lacks explicit mention of how status_filter behaves, but the schema's enum and default fill that gap. Given the presence of an output schema, the description is adequately complete.

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 0%, so the description must compensate for parameter meaning. It does not explicitly explain the 'node' parameter, though 'across all nodes' hints at its role, and it completely omits the 'status_filter' parameter. The schema's enum and defaults provide some clarity, but the description adds little beyond the structured data.

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 the specific verb 'List' with a clear resource 'LXC containers' and scope 'across all nodes', also enumerating returned fields. This distinguishes it from sibling pve_list_vms, which lists VMs, so the purpose is unmistakable.

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 implies use when needing to list LXC containers, and sibling names suggest alternatives, but it does not explicitly state when to use this tool vs. alternatives or any exclusions. No direct comparison to pve_list_vms is given.

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