Lucky host and module status

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile effectively. The description adds the crucial behavioral limitation 'Process kill is not available,' which is meaningful context beyond annotations, telling the agent that even though processes are listed, killing them is not possible. This is a valuable disclosure. It could further mention that the tool only reads current state and does not guarantee real-time data, but the provided limitation is strong.

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?

The description is a single, compact sentence that efficiently lists the covered areas in a readable sequence, followed by a clear negative constraint. No word is wasted, and the most important functional content is front-loaded. This is exemplary conciseness.

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?

Given that this is a read-only, zero-parameter status tool without an output schema, the description sufficiently conveys what information can be expected (host overview, connections, processes, modules, network interfaces) and its key limitation (no process kill). It does not detail the exact response format, but that is often discoverable from the tool's actual output. The main gap is the absence of a pointer to distinguish this from 'lucky_status', which would help complete the contextual picture for an agent choosing among siblings.

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?

The tool has zero parameters, so the schema trivially covers 100% of them. With no parameters to explain, the description does not need to add parameter meaning. Per the baseline for zero-parameter tools, a score of 4 is appropriate; there is nothing to compensate for and no ambiguity.

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 clearly enumerates the resource areas covered (host overview, connections, processes, module overview, network interfaces), making it evident that this tool provides a broad status snapshot of the host. However, it lacks an explicit verb like 'get' or 'show', and it does not explicitly differentiate from the sibling 'lucky_status' which likely serves a similar purpose. The specificity of 'host' plus the content list earns a 4, but the absence of a strong action verb and sibling distinction prevents a 5.

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 is given about when to use this tool versus alternatives. The only extra note, 'Process kill is not available,' is a negative constraint but does not explain when to choose this tool over 'lucky_status' or other related list/status tools. There is no context about scenarios such as 'use this for host-level diagnostics' or 'prefer lucky_status for global status.' This leaves the agent without clear routing.

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