proxmox_pool

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

With no annotations provided, the description carries full burden. It discloses that CRUD operations are possible (via action enum), but does not detail side effects, authorization needs, or consequences of destructive actions like 'delete' or 'update'. The behavioral transparency is minimal.

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 concise sentence that efficiently conveys the purpose. However, it could be more structured (e.g., separate explanations for each action) to improve readability. It is appropriately sized but slightly under-detailed for a multi-action tool.

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 has 5 parameters and supports multiple actions, the description lacks detail on how actions relate to parameters, what responses look like (no output schema), and prerequisites. The context is insufficient for an agent to correctly invoke the tool across all actions.

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 input schema already has 80% coverage with parameter descriptions. The tool description adds no additional meaning beyond listing actions. The schema's 'action' enum covers the operations, so the description does not augment parameter understanding.

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 tool manages resource pools and lists the specific actions (list, get, create, update, delete). It distinguishes from sibling tools which target other resources (e.g., proxmox_ceph_pool, proxmox_acl).

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?

No explicit when-to-use or when-not-to-use guidance is provided. The description implies usage for managing Proxmox resource pools, but there are no alternatives or exclusions mentioned, leaving interpretation to the agent.

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