port_forward

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

With no annotations, the description carries full burden but fails to disclose behavioral traits such as that the forward creates a long-lived connection, requires specific permissions, or that a sibling 'stop_port_forward' exists to terminate it. This is a significant gap.

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?

While the description is a single concise sentence, it is under-specified for the tool's complexity. Critical details about parameters and behavior are omitted, making the conciseness a detriment rather than a benefit.

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 5 parameters, no output schema, and no behavioral annotations, the description is grossly incomplete. It lacks information on how the forward works (e.g., background execution, port conflict handling) and does not explain the parameters, leaving an AI agent with insufficient context to use the tool correctly.

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 0% description coverage, and the description adds no parameter meaning. For example, 'resourceType' and 'resourceName' are unexplained, and the role of 'localPort' vs 'targetPort' is ambiguous without context. The description completely fails to clarify parameter semantics.

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 clearly states the action (forward a local port) and target (a port on a Kubernetes resource). It distinguishes from siblings like 'exec_in_pod' or 'stop_port_forward' by focusing on port forwarding, but could be more specific about resource types (e.g., pod, service).

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 description provides no guidance on when to use this tool versus alternatives like 'exec_in_pod' or 'kubectl port-forward'. It does not mention prerequisites, scenarios, or when not to use it.

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