create_network

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

The description goes well beyond the readOnlyHint annotation by explaining the tool's actual non-mutating advisory behavior, why it exists, and what it does not do. It adds valuable context about EasyPanel's automatic network management that the annotation alone does not convey.

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 well-structured and efficiently front-loads the most important fact: it is advisory and does not create anything. The IMPORTANT section and Args list are concise, and every sentence contributes essential information without unnecessary filler.

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 simple advisory nature, the description fully covers purpose, non-mutating behavior, parameter semantics, and the correct alternative workflow. The presence of an output schema means the description does not need to explain return values, and nothing critical is missing.

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 0%, so the description must compensate for missing parameter documentation. It provides brief but meaningful definitions for all three parameters: name, internal, and driver, including the key semantic detail that internal means isolated from the internet. This is adequate, though not deeply detailed.

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 this is an advisory helper that returns guidance rather than performing creation. It explicitly corrects the misleading tool name by saying 'This tool does NOT create anything', which fully disambiguates it from a typical create operation and from sibling tools like create_service.

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 explicitly explains when not to use this tool: there is no API to create a network directly, and EasyPanel manages networks automatically. It also provides the correct alternative, telling the agent to set internal=true when creating a service instead, which is actionable and specific.

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