vpc_get_private_network

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

The description indicates a read operation ('get details'), but with no annotations provided, it does not disclose any additional behavioral traits such as permissions, rate limits, or side effects. For a simple retrieval operation, this is adequate but not highly informative.

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, clear sentence with no unnecessary words. It is front-loaded and directly conveys the tool's purpose.

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's simplicity, the presence of an output schema, and full schema coverage, the description sufficiently covers the essential information. The agent can correctly invoke the tool with the required ID parameter.

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 input schema has 100% description coverage; the description adds no new meaning beyond the schema's parameter descriptions. It mentions the identifier but does not clarify region defaults or other nuances, so it meets the baseline.

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 retrieves details of a single Private Network by ID. It uses a specific verb ('Get details of') and resource ('Private Network'), and the context of sibling tools like vpc_list_private_networks makes the distinction 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 for retrieving a specific network by ID, but does not explicitly state when to use this tool versus alternatives like vpc_list_private_networks or vpc_create_private_network. No exclusion criteria or prerequisites are mentioned.

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