network_remove

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states 'Remove' without detailing consequences, reversibility, permission requirements, or behavior when the network is in use or does not exist. The 'force' parameter is in the schema but not described in the tool description, leaving the operational impact undocumented.

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 extremely concise, using a single sentence with no filler words. However, the phrase 'one or more' adds unnecessary ambiguity and could be removed without losing core meaning, slightly detracting from ideal conciseness. Overall, it is well-structured and front-loaded.

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 absence of annotations and an output schema, the description is incomplete. It does not explain the impact of the 'force' flag, default behavior when the network is missing, or any potential side effects. A removal tool needs more context to be safely invoked, especially regarding irreversibility and error handling.

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 100%, so baseline is 3. However, the description introduces 'one or more' which conflicts with the singular string 'name' parameter, creating ambiguity rather than clarity. It does not explain how multiple networks are specified, and thus adds confusion rather than meaningful semantic value 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 the action ('Remove') and the resource ('WSL networks'). It is specific and unambiguous about the tool's core function, distinguishing it from other tools that operate on different resources (e.g., volume_remove, container_remove). The phrase 'one or more' introduces slight ambiguity, but the core purpose is 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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, situations where removal is appropriate or not, or any alternative tools. The description is a bare statement with no usage context.

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