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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds concrete consequence context ('may interrupt applications or lose unsaved work') and a prerequisite that the device be registered, authorized, and online. It does not describe failure behavior (e.g., nonexistent PID) or irreversibility beyond the destructive hint.

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?

Three short sentences: purpose and target first, risk second, prerequisite last. Every clause earns its place with no redundancy or filler.

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 no output schema, the description covers purpose, risk, and prerequisite adequately. It omits what happens on failure or whether the process tree/children are affected, which would round it out.

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%, so the description must carry parameter meaning; it explains that pid is an integer and that device_id refers to a registered, authorized, online device. That meaningfully compensates for the bare schema, though it gives no format examples or edge cases for either parameter.

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 (terminate) and resource (process) plus the exact required inputs (integer pid, device_id) and target constraints. It is clearly distinguishable from siblings like list_processes, run_command, and service_control 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?

Explicitly directs the agent to verify target and PID with list_processes before use, which is actionable routing guidance. It lacks an explicit when-not clause or mention of alternative termination paths, so it falls short of the top score.

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