network_action

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

No annotations are provided, so the description bears full burden. It states the actions but does not disclose side effects (e.g., network removal is destructive), required permissions, or idempotency. An agent cannot anticipate consequences beyond the bare action name.

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 concise sentence listing all actions. However, it could be structured to differentiate actions or provide quick reference. It earns points for brevity but loses for lack of structure in a multi-action tool.

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 performs four distinct operations with no output schema, the description is incomplete. It does not explain return values, error scenarios, or behavior after each action (e.g., connection status). An agent lacks sufficient context to use the tool reliably.

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 already defines parameters with brief descriptions, and the tool description adds no additional meaning. It does not explain how parameters interact (e.g., driver only used with create) or provide examples. Schema coverage is 0% per context, but the schema itself has parameter descriptions; still, the description fails to add value.

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 performs four specific actions (create, remove, connect, disconnect) on a Docker network. It uses specific verbs and a clear resource, distinguishing it from sibling tools like network_query which is for querying.

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 provides no guidance on when to use this tool versus alternatives. For example, it does not mention that network_query should be used for inspecting networks, nor does it give any prerequisites or when-not conditions.

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