List SDN subnets

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

The description adds minimal behavioral context beyond what annotations already provide. Annotations indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's claim that it lists subnets is consistent and adds no extra behavioral detail (e.g., pagination, permissions).

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 a single concise sentence that front-loads the purpose. It could be slightly improved by adding more value without becoming verbose, but it is not overly concise to the point of being unhelpful.

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 low complexity (1 parameter, no output schema), the description is mostly adequate. However, it lacks a description for the 'vnet' parameter and any mention of return structure, which would make it more complete. Annotations cover safety traits.

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 0%, meaning the parameter has no description in the schema. The description only mentions 'vnet' implicitly and does not add details about expected format (e.g., ID or name) or constraints, leaving the parameter semantics unclear.

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) and the resource (subnets within an SDN vnet). It distinguishes from siblings like 'get_sdn_subnet' and 'create_sdn_subnet' by indicating it lists all subnets.

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 implies when to use the tool (to view all subnets in a vnet) but does not explicitly guide when not to use it or mention alternatives like 'get_sdn_subnet' for a specific subnet. Given the large number of sibling list tools, more explicit usage guidance would be beneficial.

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