Список port forwarding

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

With no annotations to rely on, the description carries the full behavioral burden and it only says 'current port forwarding rules'. It does not disclose that the tool reads without side effects, what shape the result takes, whether it reflects active/effective rules, or how it is affected by siblings such as add_port_forward.

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 very short and front-loaded, with no filler words or structural complexity. It is concise, though it gets some conciseness from omitting the explicit verb rather than from being a complete, clear sentence.

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 zero-parameter list tool, naming the resource is enough to make the tool callable. However, the absence of an output schema and annotations means the agent still lacks clarity about what the tool returns and what guarantees it offers beyond the label.

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 zero parameters, so there are no parameter semantics to document. The baseline of 4 applies because no parameter information is needed and nothing is missing on that front.

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 identifies the resource being acted on (current port forwarding rules) but uses a noun phrase rather than an explicit verb like 'list' or 'retrieve'. The agent can infer the action from the tool name and title, but the description itself does not state it, so the purpose is somewhat implicit.

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 about when to use this tool or why it should be preferred over related tools. The sibling tools add_port_forward and remove_port_forward suggest a read/modify split, but that distinction must be inferred rather than stated.

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