proxmox_script_list

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

No annotations are provided, so the description carries the disclosure burden. The verb 'List' and the word 'catalog' imply a read-only operation, which is useful, but the description does not mention whether it fetches live data from the community repository, whether network access is required, or what fields the returned catalog contains.

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, front-loaded sentence that states the action and the source without wasted words. Every element contributes to the agent's understanding of what the tool returns and from where.

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 zero-parameter list tool with no annotations and no output schema, the description is mostly complete: it identifies the resource and source. It could additionally mention the output shape, but the listing nature of the tool makes the missing detail a minor gap.

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 tool takes zero parameters, and the schema coverage is 100%, so there are no parameter semantics to document. The description does not need to add parameter meaning, and the baseline for a no-parameter tool 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 a specific verb ('List') and a clear resource ('curated Proxmox VE Community Scripts catalog'), and names the upstream source repo. This makes it immediately distinguishable from sibling tools like proxmox_script_command, which implies execution rather than listing.

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 intended use is implied: call this when the user wants to see the available community Proxmox scripts. However, there is no explicit when-to-use versus alternatives, such as 'use proxmox_script_command to run one of these scripts,' so guidance is only implicit.

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