reverse_port

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It only defines the direction and one example; it does not mention persistence of the reverse mapping, prerequisites like a connected device, failure modes, or the effect of the noRebind flag. This is sparse for a networking mutation.

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 that is immediately clear and includes a concrete example. It has no filler, does not repeat schema content, and efficiently conveys purpose and one key use case.

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?

The schema fully documents all parameters and required fields, and the description gives a crisp purpose with a canonical use case. Still, the absence of annotations and output schema leaves behavioral and alternative-usage details unexplained, so it is not a fully complete picture but is sufficient for basic selection and invocation.

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?

All four parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description does not add significant meaning beyond 'device' and 'local host', and the 'tcp:8081' example is already present in the schema. It maps loosely to parameter roles but adds little new semantic detail.

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 ('Reverse') and resource ('socket connections') and clearly states direction ('from a port on the device to a port on the local host'). The React Native bundler example reinforces a concrete use case, and the direction implicitly distinguishes it from the sibling forward_port without being ambiguous.

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?

It provides a clear, actionable context: 'critical for React Native bundler reverse tcp:8081', which tells the agent a canonical scenario. However, it does not explicitly contrast with forward_port or list_reverses, nor does it state when not to use this tool, so exclusions are missing.

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