vnet_subnet_show

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

No annotations are provided, so the description must fully disclose behavioral traits. It indicates a 'Show' operation, implying read-only, but does not explicitly state permissions, side effects, or output constraints. The description is adequate but minimally transparent.

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 highly concise with two sentences and an argument list. No unnecessary information; every part is relevant. It is front-loaded with the main 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?

Given that an output schema exists, the description does not need to detail return values. It mentions key output components (NSG, route table, delegations). However, it could briefly note that other subnet properties are included. Overall, it is reasonably complete.

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?

The input schema has 0% description coverage, so the description compensates by providing brief but clear meanings for each parameter: 'vnet_name: Virtual network name', 'subnet_name: Subnet name', 'resource_group: Resource group containing the VNet'. This adds value beyond the schema titles.

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's purpose: 'Show details of a subnet including NSG, route table, and delegations.' It uses a specific verb ('Show') and resource ('subnet details'), and this distinguishes it from sibling tools like vnet_subnet_list (which lists subnets) and vnet_subnet_create (which creates).

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?

No explicit guidance on when to use this tool versus alternatives (e.g., vnet_show, vnet_subnet_list). The description implies usage for obtaining detailed information about a specific subnet, but lacks comparative context or prerequisites.

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