pve_sdn_subnet_create

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

Discloses mutation, dry-run by default (returns PLAN), and that confirm=True creates pending subnet returning {status, result}. Mentions RISK_LOW (staging; inert until apply). Could elaborate on permissions or side effects of applying, but sufficient.

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 plus sibling references. Each sentence is meaningful and front-loaded with 'MUTATION'. No wasted words.

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 output schema exists (indicated) and full parameter coverage, description explains core behavior (pending, dry-run, apply). Could mention error conditions or prerequisites, but complete enough for creation 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 coverage is 100%, so baseline 3. Description adds value by explaining 'subnet' is CIDR, 'options' carries gateway/snat/dhcp, and 'confirm' controls dry-run vs execution. Does not elaborate on vnet, lock_token, proximo_target beyond schema.

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 it's a mutation to create an SDN subnet, specifies that 'subnet' is a CIDR (e.g., 10.0.0.0/24), and mentions it is pending. It distinguishes from sibling tools pve_sdn_subnet_update and pve_sdn_subnet_delete.

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?

Explicitly tells when to use this tool (create) and when to use alternatives (update/delete). Also explains dry-run default behavior and how to execute using confirm=True.

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