pve_sdn_zones_list

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

The description marks the tool as 'read-only', disclosing its non-destructive nature. While no annotations are provided, this key behavioral trait is clearly stated, though additional details like authentication or rate limits are absent.

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 three concise sentences that immediately convey the tool's purpose, return values, and related tools. Every sentence adds value, and it is front-loaded with the core action.

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 existence of an output schema, the description adequately covers the tool's purpose, usage, and return fields. It also references relevant sibling tools, making it sufficiently complete for a list operation.

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%, and the description does not add extra meaning beyond what the schema already provides for the single parameter proximo_target. The parameter is well-documented in the schema, so the description offers no additional semantic value.

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 'List SDN zones in the cluster (read-only)' with a specific verb and resource, and distinguishes from siblings by mentioning pve_sdn_zone_create and pve_sdn_apply for related operations.

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 explicitly says when to use this tool (list SDN zones) and provides alternatives for adding (pve_sdn_zone_create) and committing (pve_sdn_apply), offering clear usage guidance.

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