list_sdn_subnets

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

No annotations are present. The description only states the basic function without disclosing behavioral traits such as read-only nature, required permissions, or side effects. It does not add value beyond the basic purpose.

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 very brief (two sentences). While concise, it omits necessary details like output description or usage notes, resulting in under-specification rather than efficient conciseness.

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 the tool has a single required parameter and an output schema, the description is only partially complete. It does not explain that the VNet must exist, what the output contains beyond 'subnets', or any error conditions. The output schema compensates for return format, but broader context is lacking.

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 minimal value: it labels the parameter 'vnet' as 'VNet ID', which is already implied by the schema name 'vnet'. With 0% schema description coverage, the description should provide more detail (e.g., format, usage), but it does not.

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 action (List subnets) and the resource (SDN VNet). However, it does not explicitly distinguish this tool from sibling 'list_sdn_vnets' or other list tools. The phrasing 'for an SDN VNet' implies it is scoped to a specific VNet, which offers some differentiation.

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 is provided on when to use this tool versus alternatives like list_sdn_vnets for listing all VNets. The description does not mention any context or constraints.

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