vnet_subnet_create

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

No annotations provided, so description bears full burden. It does not disclose side effects (write operation), required permissions, error conditions, or behavior when the subnet already exists. Merely states action without behavioral context.

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 short and to the point, with a clear arg list. It is efficient but could include a sentence on prerequisites or return value without becoming verbose.

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?

With an output schema present, return values need not be explained, but the description lacks context about required preconditions (VNet existence, prefix validity) and doesn't cover error scenarios. It is adequate but not fully complete for a creation tool with 4 required params.

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 description adds meaning beyond the input schema by naming and explaining each parameter (e.g., 'Virtual network name', 'Subnet CIDR (e.g. 10.0.1.0/24)'). Schema has 0% description coverage, so this is valuable, though could be more detailed (e.g., prefix format constraints).

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 'Create a subnet in a virtual network' clearly specifies the verb (create) and resource (subnet in vnet), and the name distinguishes it from sibling tools like vnet_subnet_delete or vnet_subnet_list.

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 guidance on when to use this tool vs alternatives. No mention of prerequisites (e.g., VNet must exist, address prefix must be within VNet range) or conditions under which creation is appropriate.

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