port_off

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

The description explicitly warns that the server will lose network connectivity on the interface, adding meaningful context beyond the destructiveHint annotation. It does not contradict the annotations and helps the agent anticipate the operational impact.

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, front-loaded sentence that states the action and the key destructive consequence. Every word earns its place; there is no redundant or irrelevant content.

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 simple destructive toggle operation with a confirm parameter, the description and schema together are sufficient. It could mention reversibility via port_on, but that is not essential for correctly invoking this tool.

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 describes all three parameters at 100% coverage, including the confirm flag and the port source. The description does not add additional parameter-level meaning, so the baseline score of 3 applies.

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 ('turn off the server network port') and identifies the resource ('server network port'). It is specific enough to be distinguished from the sibling port_on by its opposite operation, though it does not explicitly name the sibling.

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?

No guidance is provided on when to use this tool versus alternatives like port_on, nor on prerequisites such as checking current connectivity via get_network_status. The destructive effect is stated, but the intended use context is left implicit.

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