pve_sdn_subnet_list

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

With no annotations, the description carries the burden. It explicitly states it is READ-ONLY and notes that the exact output field set is not guaranteed, which are key behavioral traits. However, it does not mention authorization needs or rate limits.

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 exceptionally concise: two sentences that cover purpose, read-only nature, output caveat, and references to related tools. 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?

Given the presence of an output schema (not shown) and the description's warning about unstable output fields, the tool is well-contextualized. It covers the essential aspects for a straightforward list operation, though it does not explain prerequisites like existing vnets.

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 100%, so the schema already provides clear meanings for both parameters (vnet and proximo_target). The description adds no further parameter details, earning the baseline score of 3.

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 lists subnets configured in a vnet, the verb 'list' and resource 'subnets' are specific, and it distinguishes itself from siblings by mentioning pve_sdn_subnet_create and pve_sdn_apply for related actions.

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 hints at when to use related tools ('Use pve_sdn_subnet_create to add one and pve_sdn_apply to commit') but does not provide explicit guidance on when to use this tool versus alternatives or any exclusions.

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