Groups

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

Annotations already convey readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description adds the explicit action set (create/update/delete), which aligns with the destructive annotation. However, it adds no context about side effects, permissions, or behavior beyond what the annotations and schema already state.

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 with no filler. It efficiently names the resource and the four actions, earning its place. It is slightly terse but appropriately concise for the scope.

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 multi-action CRUD tool with 7 parameters and no output schema, this description is minimal. It lacks context about group semantics, update behavior (e.g., replacing vs. appending users), or effect of the digest parameter. The agent must rely entirely on the schema to understand call semantics, which is a notable gap for confident 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?

Schema description coverage is 86%, so the schema already documents most parameters (users, append, delete, digest, comment, groupid). The description adds no parameter-level meaning beyond the action list, which is also captured by the action enum. With high schema coverage, a baseline of 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 a specific verb 'Manage' with the resource 'Proxmox groups' and enumerates the supported actions: list, create, update, delete. This makes the scope clear and distinguishes it from many sibling tools, though it does not explicitly differentiate itself from proxmox_ha_group or other group-adjacent 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 gives no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or reasons to prefer a sibling tool like proxmox_user or proxmox_role. The agent must infer usage solely from the generic action list.

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