remove_network

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

The description states 'Destructive' and 'requires confirmation token', which warns about irreversibility and an extra step. However, without annotations, it lacks details on what exactly is destroyed (e.g., whether associated resources like containers or settings are affected) or how the confirmation token is provided.

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, comprising two short sentences with no redundant information. Every word serves a purpose: 'Remove a network' for action, 'Destructive' for behavior, and 'requires confirmation token' for constraint.

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?

For a tool with 3 parameters, no output schema, and no annotations, the description is too minimal. It fails to explain return values, side effects, or the meaning of parameters, leaving significant gaps in understanding for the agent.

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 includes three parameters (env_id, network_id, agent_token) with 0% schema description coverage, but the description does not explain any of them. The agent cannot infer the meaning of env_id, how to use agent_token for confirmation, or that network_id is required.

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 verb 'Remove' and the resource 'a network', making the tool's primary action explicit. However, it does not distinguish this from sibling tools like 'remove_container' or 'remove_environment' beyond the resource type, missing an opportunity to clarify scope or context.

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 such as 'prune_networks' or 'disconnect_container_from_network'. It does not mention prerequisites, when not to use it, or any scenarios where another tool would be more appropriate.

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