test_port

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, lowering the bar for additional disclosure. The description adds meaningful context that the check is performed from outside, clarifying the network semantics. It does not detail latency or exact reachability criteria, but for a zero-parameter diagnostic this is adequate.

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 filler, front-loading the verb and object. Every word contributes to understanding the tool's purpose.

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 zero parameters, a strong annotations set indicating a safe read-only operation, and an output schema, the one-sentence description is sufficient for an agent to invoke the tool correctly and interpret its result. Nothing critical is missing.

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 has no properties, so there are no parameter semantics to clarify. The description correctly focuses on the operation rather than attempting to document nonexistent parameters, matching the baseline for zero-parameter tools.

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 uses a specific verb ('check') and a specific resource ('peer port') and clearly states the condition being tested ('reachable from outside'). This is easily distinguishable from the sibling torrent-management tools, none of which perform connectivity checks.

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 sentence conveys the clear intended use case: verify whether the peer port is externally reachable. It does not explicitly name alternatives or exclusions, but no sibling tool competes with this functionality, so the context is sufficiently clear.

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