Check port

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that it measures latency, which is useful behavioral context. However, it does not disclose behavior on failure (e.g., timeout, error handling) or what the output contains, but the output schema presumably covers that. No contradiction with 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 a single sentence with no wasted words. It front-loads the action and includes the key metric. This is appropriately concise.

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 that an output schema exists, the return values are covered. However, the description lacks any mention of when to use it, timeout behavior, or error semantics. For a simple check tool it is adequate but not complete, especially with many sibling tools that overlap in function.

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 0%, so the description must compensate, but it does not. It only implies 'host:port' but does not explain the meaning of host (default given in schema) or port format. The description adds minimal value beyond parameter names; with zero coverage, this is a significant gap.

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 states a specific action ('TCP connect') and resource ('host:port'), and mentions the metric 'latency'. It clearly conveys what the tool does, and the action distinguishes it from port_owner (owner lookup) and port_list (list ports). However, it does not explicitly say 'check reachability' or 'test connectivity', so it leaves some inference.

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?

There is no guidance on when to use this tool versus alternatives like network_check, http_fetch, or port_list. The description does not mention any conditions, exclusions, or preferred use cases. An agent would have to infer from the name and siblings.

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