SDN Subnets

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

The annotations already convey readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the description does not need to restate those. It adds no extra behavioral context such as prerequisites, cascading effects, or operation-specific side effects, but it also does not contradict the annotations.

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?

One short sentence front-loads the resource and lists all supported operations with no filler. Every word earns its place.

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 13-parameter, five-action CRUD tool with no output schema, this description is too thin. It never explains which parameters are required for create/update/delete, what list/get return, or any per-action constraints, leaving the agent to infer critical invocation details from the schema alone.

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 92% and most parameters are documented in the input schema. The description adds no parameter-level meaning beyond echoing the action enum, so the baseline score of 3 applies.

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 names the resource 'SDN subnets' and enumerates the five CRUD operations, which distinguishes it from sibling SDN tools like proxmox_sdn_vnet and proxmox_sdn_zone. However, 'manage' is a generic umbrella verb rather than a specific action; the parenthetical carries the actual specificity.

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?

No guidance is provided about when to use this tool versus related SDN tools, nor which action is appropriate in a given scenario. The only usage signal is the implicit resource name, which is insufficient for a polymorphic CRUD tool with multiple sibling tools.

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