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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds genuine beyond-schema context: that killing a ReMCP session's PID can leave session state and process trees inconsistent, which is exactly the kind of side-effect warning annotations cannot express. It stops short of stating failure behavior or irreversibility explicitly, so not a 5.

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, front-loaded with the primary use case and followed by the disambiguation. Every clause carries information; no filler or restatement of the tool name.

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 two-parameter destructive tool with full schema coverage, an output schema, and annotations covering the safety profile, the remaining burden on the description is disambiguation and side-effect warning, both of which are present. An agent has everything needed to select and call it 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?

Schema description coverage is 100%, with both pid and device documented inline, so the baseline is 3. The description only names the PID concept and adds no format, range, or meaning beyond the schema, nor does it explain the device requirement.

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 specific verb+resource: stopping an arbitrary operating-system process by PID. It also explicitly distinguishes itself from the sibling force_terminate by naming the condition (ReMCP terminal session created by start_process) that selects the alternative.

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?

Gives an explicit when-to-use clause ('when the user wants to stop an arbitrary operating-system process by PID') and an explicit when-to-prefer-something-else clause pointing at force_terminate with the reason (session state and process tree handled consistently). Nothing is left to inference.

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