layerfs_operator_process_cancel

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is known. The description adds only that the target is a background process; it says nothing about how cancellation is delivered, what happens to buffered output or exit status, or what an already-terminated or unknown id produces — a real gap for a destructive, non-idempotent 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?

A single front-loaded sentence with no filler and the identifying constraint placed at the end of the clause. Efficient, though terseness here edges toward under-specification rather than economy.

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?

Destructive, non-idempotent, one parameter at 0% schema coverage, and no output schema — the description would need to explain the effect of cancellation and the failure modes. Neither is covered, so an agent cannot predict what happens to the process or its output.

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 coverage is 0%, so the description must carry the parameter, and it partially does: 'persisted process id' rules out an OS PID or a process name. It still doesn't say where that id is obtained (process_start/process_list output) or whether it must be the full id.

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 and resource — cancel a background process — plus the identifier type ('persisted process id'), which separates it from layerfs_operator_process_start and process_list. It doesn't explicitly name the sibling it replaces, but the action is unambiguous.

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?

Usage is implied: call this when you need to stop a running background process, and the phrase 'persisted process id' hints the id comes from a prior start/list call. There is no explicit when-not condition (e.g. already-finished processes) and no named alternative.

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