portainer_network_create

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

With no annotations, the description carries full burden. It discloses default driver ('bridge') and mentions 'overlay for Swarm' and internal restriction, but it omits side effects (e.g., error on duplicate network), idempotency, permissions, and the return value (though an output schema exists, it's not described).

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: one-line purpose followed by a bulleted parameter list. Every sentence adds value, and it's front-loaded with the action. No unnecessary words.

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?

The description covers parameter semantics well, but lacks behavioral details (e.g., what happens if network already exists, error handling) and usage guidance (e.g., when to use this vs other network tools). The output schema exists but is not referenced, leaving the agent to infer return format.

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 0%, so description explains all parameters: name (required), driver (default 'bridge', 'overlay' for Swarm), internal (restricts external access), labels (optional key-value), endpoint_id (target endpoint, default omitted). This adds meaningful context beyond 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?

The description clearly states 'Create a Docker network,' using a specific verb and resource. It distinguishes itself from sibling tools like network_connect, network_disconnect, network_inspect, network_remove, and networks_list, all of which serve different purposes.

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 by listing parameters and providing a driver hint (overlay for Swarm), but it does not explicitly state when to use this tool versus alternatives, nor does it specify prerequisites or conditions such as requiring an existing endpoint.

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