List network appliances

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

Goes beyond the annotations (readOnlyHint, idempotentHint, destructiveHint=false) by disclosing the required auth scopes, that default grants do not cover networking, and that the backend enforces ownership, feature availability and 2FA locks. The mention of 'networking:manage for changes' is slightly confusing on a read-only tool but not contradictory.

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 dense sentences, front-loaded with what is read and the stream behavior, followed by permission constraints. Slightly compressed with semicolons but no wasted text.

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 no output schema and no parameters, the description covers the essential operational context an agent needs: what is returned (load balancers + VPN gateways), the streaming nature, and the auth requirements. An explicit pointer to the narrower list siblings would make it fully 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 tool takes no parameters, so there is no per-parameter semantics to document; baseline 4 applies. The phrase 'one stream cursor' hints at a pagination/streaming model, though no cursor parameter is exposed in the schema.

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?

States a specific verb ('Read') and resource ('owned load balancers and VPN gateways'), which is more informative than the bare title. It implies aggregation of two appliance types into one stream, but does not explicitly distinguish itself from the sibling tools list_network_load_balancers and list_network_vpn_gateways.

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?

Provides permission context (networking:read vs networking:manage) and notes that full/read defaults do not grant networking, which helps an agent decide whether it can call the tool. However, there is no explicit when-to-use/when-not guidance versus the per-type list siblings that cover the same resources.

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