vpc_create_private_network

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

The description discloses that the network is tagged with 'created_by=scaleway-mcp' for safe deletion, adding value beyond the schema. However, it does not describe other behavioral traits like idempotency, response details, or potential side effects. Without annotations, this is partially informative but not comprehensive.

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 sentences, front-loaded with purpose, no extraneous information. Every sentence 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?

Given the presence of an output schema and full parameter descriptions, the description is fairly complete. It could include more on the networking context (e.g., relationship to VPCs), but it covers the essential tagging behavior. No major gaps.

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 coverage is 100% with each parameter described. The description does not add any additional parameter semantics; it only reiterates the tagging behavior. Baseline of 3 is appropriate since the schema already handles parameter documentation.

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 'Create a Private Network' with a specific verb and resource. It distinguishes from sibling tool vpc_create_vpc which creates a VPC, not a private network. However, it does not explicitly differentiate from other create tools.

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?

No guidance on when to use this tool versus alternatives, such as when to attach to a VPC or use default VPC. No exclusion criteria or context provided.

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