harvester_subnet_list

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

The description indicates a list operation (read-only), but the annotations set destructiveHint=true, creating a contradiction. The description does not acknowledge or clarify this discrepancy or disclose any other behavioral traits.

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 sentence that conveys the purpose and a key prerequisite without any fluff. Every word 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?

The description gives basic context about what subnets are and their linkage to networks, but it does not describe the output format or behavior (e.g., pagination via continue token). The lack of output schema and the annotation contradiction reduce completeness.

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 the baseline is 3. The description adds no additional meaning beyond the parameter names and types already present in the 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 the tool lists KubeOVN Subnets, specifies the resource type, and provides context about their role (define VM network CIDRs, linked to Networks via provider). It distinguishes from sibling tools like harvester_network_list and harvester_vpc_list.

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 mentions a prerequisite (requires kubeovn-operator addon) and explains the relationship between subnets and networks, but does not provide explicit guidance on when to use this tool versus alternatives like network_list or vpc_list.

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