pc_fixer_kill_port_process

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that a process will be terminated, but says nothing about whether the kill is forceful, whether it is reversible, what happens if no process holds the port, or what privileges are required — meaningful gaps for a destructive tool.

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?

One sentence, front-loaded with the action, followed by the concrete resource and the outcome it enables. No filler or repeated information beyond the illustrative ports.

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 single-parameter tool with no output schema the description covers purpose and motivation adequately. Given that this is the only clearly destructive operation among the siblings and has no annotations, it would benefit from stating safety and failure behavior.

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?

There is a single required parameter with 100% schema description coverage, and the schema already documents it as a TCP port number with examples. The description's port examples (3000, 5000, 8000, 8080) largely duplicate the schema, so the baseline 3 is appropriate.

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?

States a concrete verb pair ('Find and terminate') and a specific resource ('the process locking a specific developer port'), with example ports that make the scope unmistakable. It is clearly distinct from siblings like pc_fixer_diagnose or pc_fixer_check_system, though it never names an alternative explicitly.

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 usage context is implied well ('to unblock dev servers without rebooting'), so an agent can infer when this applies. However, there is no explicit when-not guidance, no mention of checking first with pc_fixer_diagnose, and no note about confirming before killing a process.

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