stop_port_forward

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

No annotations beyond title, so description must cover behavioral traits. It does not mention what happens if an invalid id is provided, whether resources are cleaned up, or any side effects.

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, which is concise, but it under-specifies the tool by omitting critical context. It earns its place but could be expanded without becoming verbose.

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 annotations, no output schema, and an undocumented parameter, the description fails to provide enough context for correct invocation, especially regarding the meaning of 'id' and the tool's relationship to 'port_forward'.

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 parameter 'id' has no description (0% coverage). The description adds no information about what the id represents, leaving the agent with no clue about its meaning.

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 'Stop a port-forward process' uses a specific verb and resource, clearly distinguishing it from the sibling tool 'port_forward' which presumably starts one.

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 on when to use this tool versus alternatives, no prerequisites or conditions mentioned. The description lacks context about the required state (e.g., need an active port-forward).

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