Sm Process Operations

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

With no annotations, the description carries the full behavioral burden and largely drops it: nothing says that kill_process is destructive or irreversible, that it needs elevated privileges, or what any action returns. The word 'managing' is the only hint that mutation is possible.

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 short sentence with no filler; the problem is under-specification rather than verbosity. It is front-loaded but there is almost nothing to front-load.

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 tool that can terminate processes with no annotations and no output schema, the description should say what each action does and what the destructive one affects. The agent must infer everything from the action enum string names alone.

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 action enum values are fully enumerated in the schema, so the description need not repeat them. It adds no meaning beyond the schema, so the baseline 3 applies.

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?

The description restates the tool name almost verbatim: 'Operations for managing system processes' adds only the resource noun over 'sm_process_operations'. It never names the actual operations (list, inspect, terminate), so an agent learns more from the schema's action enum than from the description.

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?

No guidance on when to use this versus siblings such as get_process_details or sm_system_operations, which plausibly overlap. There are no stated preconditions, no mention of when the destructive action is appropriate, and no exclusions.

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