port_on

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

Although annotations declare readOnlyHint=false, the description itself adds no behavioral disclosure. It doesn't mention that the tool permanently changes the port state, that the `confirm` flag is mandatory, or any operational consequences. Since annotations already declare the safety profile, the description adds little beyond what can be inferred from the name and schema.

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, focused sentence with no filler words, and the first and only clause states the primary action. Some helpful context is missing, but the size is concise and the main purpose is 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?

For a simple three-parameter mutation with 100% parameter coverage and pre-populated annotations, the description is enough for identification and basic invocation but doesn't provide guidance such as sequencing or the effect of the `confirm` flag. Given the small tool, this is adequate but not complete.

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 the description is not required to explain parameters. In addition, the tool description includes no parameter meaning beyond the schema, so a baseline 3 is appropriate.

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 a specific action ('enable') and a specific resource ('server network port'), and it is not a tautology. However, it does not explicitly distinguish the tool from its sibling `port_off` or other network-related tools, so it doesn't earn a 5.

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 zero guidance on when to use this tool instead of alternatives, or about any prerequisites or post-conditions. The hint about `port` coming from `get_network_status` is useful, but it is in the schema parameter description, not in the main description.

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