port_forward

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

Annotations provide no behavioral hints. The description only repeats the purpose. It does not disclose that the port forward runs in the background, requires a running process, or how to stop it. No mention of potential side effects or resource usage.

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 concise sentence with no wasted words. However, it sacrifices necessary detail for brevity. It could be expanded slightly without losing conciseness.

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 the tool has 5 parameters, no output schema, and no annotations, the description is woefully inadequate. It does not cover return values, lifecycle (how to stop), or error states (e.g., port already in use). The agent would need to infer too much.

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 description coverage for its 5 parameters. The description does not explain any parameter meanings, such as what resourceType values are valid (e.g., pod, service), or the difference between localPort and targetPort. This leaves the agent guessing.

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) and the resource (local port to a Kubernetes resource). It is specific, but does not differentiate from sibling tools like exec_in_pod, which also involve connecting to a pod. No mention that this is similar to kubectl port-forward.

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 on when to use this tool versus alternative tools such as exec_in_pod or kubectl_get. Missing context like prerequisites (e.g., pod must be running) or use cases (e.g., debugging a database).

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