update_vng_azure

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

The description labels the operation as destructive and requires confirmation, but lacks details on what exactly is destroyed or the consequences of the update. With no annotations, the description carries the full burden, and more behavioral context would be beneficial.

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 extremely concise, with five lines covering essential information. No redundant words, and the structure flows logically from purpose to parameters.

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 covers purpose, usage, and parameters adequately given the tool's complexity. However, missing prerequisites (e.g., Azure account setup, permissions) and does not mention the output schema's contents, though that is not required.

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?

Since the schema has 0% description coverage, the description adds meaningful context: vng_id includes an example, updates_json is explained as a JSON string of fields, and confirm is described as a safety guard. Account_id is briefly explained.

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 updates an Azure VNG configuration, explicitly mentioning it is destructive. The 'azure' suffix differentiates it from the sibling tool 'update_vng'.

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 emphasizes the requirement for confirm=true as a safety guard, providing clear usage guidance. However, it does not explicitly state when to use this tool over alternatives like update_vng or when not to use it.

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