pve_group_create

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

Discloses mutation, default dry-run behavior, low risk, and the inert state of created groups. No annotations provided, so description covers key behavioral traits adequately.

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?

Two sentences, front-loaded with purpose and key behavior. No filler, every sentence adds value.

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?

Covers core usage, execution flow, and post-creation state. Output schema exists, so return values don't need elaboration. Lacks prerequisites or error handling details, but sufficient for a simple tool.

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 only 25% (only proximo_target described). Description adds meaning to confirm parameter (dry-run vs execute) but comment and groupid lack additional detail beyond schema titles.

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?

Clearly states it creates an empty group. Distinguishes from siblings like pve_group_get, pve_group_update, pve_group_delete, and pve_groups_list by specifying 'create' and 'empty'.

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?

Explains dry-run mode, risk level, and the need for confirm=True to execute. Describes that the group is inert until users or ACL are added, guiding post-creation steps. Could more explicitly contrast with sibling tools.

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