Delete SDN subnet

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

Annotations already provide destructiveHint=true and readOnlyHint=false. The description adds the instruction to ask for user confirmation, which reinforces the destructive nature. However, it does not disclose additional behavioral traits such as cascading deletes or prerequisites, relying heavily on 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?

The description is two sentences: first states the action, second provides a critical warning. It is extremely concise with no wasted words, front-loading the purpose.

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 tool is destructive with 3 parameters and no output schema. The description lacks prerequisites (e.g., subnet must exist, not in use), error conditions, or return value. For a delete operation, more context is needed to ensure correct usage.

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 only 33% (only the 'confirm' parameter has a description). The tool description does not add any parameter semantics beyond stating the action. With low coverage, the description should compensate, but it fails to explain what 'vnet' and 'subnet' refer to.

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 'Delete an SDN subnet', providing a specific verb and resource. It distinguishes from sibling tools like create, update, list, get, and other delete 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 includes 'DESTRUCTIVE — ask the user to confirm before invoking', which provides a clear when-to-use guideline (only after user confirmation). It does not explicitly mention when not to use or alternatives, but the warning is sufficient for this context.

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