Update SDN zone

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

Description adds 'HIGH RISK — ask the user to confirm' beyond annotations that already indicate destructiveHint=true and readOnlyHint=false. This provides actionable behavioral context without contradicting 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?

Single sentence effectively conveys the core message. No unnecessary text. Follows front-loading principle well.

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?

Despite good purpose clarity, the description omits crucial context for a tool with 7 parameters, no output schema, and destructive impact. Should at least hint at which fields are commonly updated or the effect of deletion.

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 low (14%), with only 'confirm' having a description. The tool description does not explain any parameter meaning or usage, failing to compensate for the schema gap.

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?

Clearly states the action (Update) and the resource (SDN zone). Distinguishes from sibling tools like create_sdn_zone, delete_sdn_zone, get_sdn_zone. The HIGH RISK warning adds 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?

Provides explicit instruction to ask user before invoking due to high risk, which is a key usage guideline. However, lacks guidance on when to use this tool vs alternatives (e.g., selecting specific parameters).

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