List isolated networks

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and repeatability are fully covered. The description adds only the account-scoping context ('in your account'); it says nothing about pagination behavior, result volume, or ordering that isn't already in the schema. With annotations carrying the behavioral load, a 3 is appropriate.

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?

Two short sentences with no filler: the scoping statement comes first and the disambiguation second. Every clause earns its place.

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?

For a simple, annotation-covered, paginated list with only two self-documented optional params, the description supplies what an agent needs to select and call it. The only gap is any hint about the shape of returned network objects, which is minor given the low complexity and the presence of get_isolated_network for detail.

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 100%, with both 'page' and 'pageSize' documented including defaults, limits, and the note to pass page to fetch more. The description adds no parameter meaning beyond that, which is the expected baseline when the schema fully documents the inputs.

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 gives a specific verb and resource ('List standalone isolated (single-tier private) networks') and immediately scopes it to the account, while explicitly distinguishing this resource from VPC tier subnets. An agent can tell this apart from list_vpc_networks / get_vpc_network without inspecting any schema.

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?

It states the condition that selects this tool (standalone isolated networks) and redirects VPC tier lookups to a sibling, which is real routing guidance. It stops short of explicitly naming list_vpc_networks for comparable listings or stating a when-not condition beyond the VPC distinction.

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