winops_sys_test_port

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds value by specifying the JSON return format and providing usage examples, increasing transparency about output and usage. It does not contradict annotations.

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, containing a one-sentence purpose, the return format, and two examples. Every element earns its place with no redundancy.

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 TCP connectivity test, the description, combined with the output schema and parameter definitions, is sufficiently complete. It lacks discussion of network-level nuances, but such details are not necessary given the tool's simplicity.

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?

With 100% schema description coverage, each parameter is already well-documented. The description adds semantic value through concrete examples (e.g., test_port(host='8.8.8.8', port=53)), which helps clarify expected usage 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 'Test TCP connectivity to a host:port' uses a specific verb ('test') and resource ('TCP connectivity to a host:port'), making the tool's purpose immediately clear. It distinguishes itself from siblings like winops_net_diag by focusing on a targeted connectivity check.

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 such as winops_net_diag or other network diagnostic tools. The description does not mention exclusions, prerequisites, or typical scenarios beyond the basic action.

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