network_disconnect

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

Describes that the container keeps running after disconnect and that only the endpoint is removed. Adds context beyond annotations (readOnlyHint=false, destructiveHint=false) by noting network deletion constraint and force use for stale endpoints. No contradiction.

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?

Concise and well-structured with a clear purpose sentence followed by args and returns. Slight redundancy in the arg descriptions could be trimmed, but overall efficient.

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 annotations and schema, the description covers purpose, parameters, return type, and behavioral context (network deletion prerequisite). No output schema but return type is documented.

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?

Despite 0% schema coverage, the description explains each parameter (id_or_name, container, force) with practical usage details (e.g., force for stale endpoints), adding meaning 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 'Disconnect a container from a network' and distinguishes it from sibling tools like network_connect (reverse) and network_remove.

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?

Explicitly advises to disconnect before network_remove because a network with connected containers cannot be deleted. Also explains force parameter for stale endpoints, providing clear when-to-use guidance.

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