proxmox_group

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

With no annotations provided, the description carries the full burden of behavioral transparency. It only says 'Manage' without detailing side effects, permission requirements, or what happens during create/update/delete. This is insufficient for an agent to understand the tool's impact.

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 very concise (one sentence) but lacks structure. It efficiently states the purpose but misses the opportunity to provide separate sections or bullet points for different actions, which would improve readability for an AI agent.

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 7 parameters and multiple actions, the description is incomplete. It does not explain return values, error handling, or usage patterns. The schema covers parameter syntax, but the description fails to provide operational context necessary for proper tool invocation.

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 provides descriptions for 86% of parameters, so the baseline is 3. The description does not add additional explanation or context beyond listing the actions. No parameter details are elaborated beyond the schema, so it meets the minimum but does not exceed.

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 that the tool manages Proxmox groups and lists the supported actions (list, create, update, delete). The verb 'Manage' combined with the resource 'Proxmox groups' gives a clear purpose, though it does not explicitly differentiate from sibling tools like proxmox_user or proxmox_role, which are about different resources.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of scenarios, prerequisites, or when not to use it. Agents would need to infer usage from the tool name and actions alone.

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