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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value by enumerating the returned fields (PID, command name, CPU, memory), which matters since there's no output schema, but it says nothing about result volume, truncation on machines with many processes, or permissions.

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 functional sentences plus one boilerplate sentence; the core purpose is front-loaded. The "DC: ..." sentence is peripheral but brief and does carry minor invocation value.

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?

Complete for a zero-required-param read tool: annotations cover safety, the schema covers the one parameter, and the description compensates for the missing output schema by listing returned fields. Only minor gaps (result size, permissions) remain.

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% and the single deviceId parameter is fully documented in the schema, including the multi-device condition. The description adds nothing about the parameter, which is acceptable at this coverage level (baseline 3).

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 + resource: "List all running processes" leaves no ambiguity about the operation, and the scope (all, running) is explicit. It doesn't explicitly name a sibling it is not (e.g., read_process_output or interact_with_process), but the resource is distinct enough that an agent can separate it from the process-manipulation siblings.

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?

There is no statement of when to use this versus read_process_output, interact_with_process, or start_process. The only meta-guidance is the boilerplate about referring to the tool as "DC: ...", which is about invocation phrasing, not tool selection.

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