list_vpc_networks

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

With no annotations, the description carries full behavioral burden. It states the return is a list of VPC networks but does not disclose permissions, side effects, pagination, or any other behavioral traits. The word 'List' implies a read operation, but this is not explicit.

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 concise and well-structured with a purpose sentence followed by Args and Returns sections. It contains no fluff and is easy to scan.

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 one-parameter tool, the description provides the essential input and output information. However, since there is no output schema, it does not describe the structure of the returned VPC networks or pagination behavior, leaving it minimally viable but not comprehensive.

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 schema has one parameter (project_id) with no description, and the description explains it as 'the ID of the GCP project to list VPC networks for,' which adds a bit of meaning. However, it lacks format examples or additional context, so it only partially compensates for the 0% schema coverage.

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 tool lists VPC networks in a GCP project with a specific verb and resource. It does not explicitly distinguish from siblings like get_vpc_details or list_subnets, but the scope and action are clear.

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 usage when you need to list VPC networks, but it does not provide explicit when-to-use guidance or alternatives among the sibling tools. There is no mention of scenarios where this tool is preferred over get_vpc_details or list_subnets.

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