stop_test_client

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

With no annotations, the description carries the burden and does disclose meaningful behavior: the two operating modes, PID/process-group targeting, and the safety property that stale/recycled PIDs cannot hit a newer process. It omits what happens on already-dead processes or failure semantics, so it is strong but not complete.

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?

Two sentences, no filler, with the core action and its origin tool front-loaded before the mode-specific constraints. Every clause earns its place.

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?

An output schema exists, so return values need not be described, and the two-mode lifecycle is covered. However, for a 6-parameter teardown tool with no annotations, the missing parameter documentation and absence of failure/idempotency notes leave real gaps.

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?

Schema description coverage is 0% across 6 parameters, so the description must compensate and largely does not. It gives meaning to pid (via PID/process group) and lifecycle_handle (remote mode), but says nothing about port, xvfb_pid, lifecycle_id, or manage_apache, leaving the majority of parameters undocumented.

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?

Specific verb (tear down) plus resource (TestClient), and it explicitly ties itself to the sibling that spawned it (launch_test_client). An agent can distinguish this from test_client_status or attach_test_client without opening any schema.

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?

It splits usage into two modes and states what each requires (PID/process group for local, lifecycle handle for remote), which is clear operational context. It stops short of outright 'use X instead of Y' exclusions against siblings like test_client_status, so it is not a full 5.

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