Linux MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions remote execution via SSH and local fallback, which is valuable context. However, it doesn't describe what 'detailed information' includes, whether this requires special permissions, potential rate limits, error conditions, or what the output looks like. For a system monitoring tool with zero annotation coverage, this leaves significant behavioral gaps.

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 efficiently structured with a clear purpose statement followed by parameter explanations. Every sentence adds value: the first establishes the tool's core function, and the parameter documentation provides essential usage context. It could be slightly more front-loaded with key behavioral information, but overall it's appropriately sized.

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 the tool's moderate complexity (process monitoring with remote capability), no annotations, and the presence of an output schema, the description does an adequate but incomplete job. It covers the basic operation and parameters well, but lacks information about permissions, error handling, output format hints, and comparison to sibling tools. The output schema existence reduces but doesn't eliminate the need for some behavioral context.

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 description provides clear semantic meaning for all three parameters beyond the 0% schema description coverage. It explains pid identifies the process, host enables remote SSH execution (optional with local fallback), and username is required conditionally with host. This fully compensates for the schema's lack of descriptions, though it doesn't specify format details like SSH host syntax.

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 states the verb ('Get detailed information') and resource ('about a specific process'), making the purpose immediately understandable. It distinguishes from siblings like 'list_processes' by focusing on detailed info for a specific process rather than listing all processes. However, it doesn't explicitly contrast with other process-related tools that might not exist in this set.

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?

The description implies usage context through the parameter documentation (local vs. remote execution), but doesn't explicitly state when to use this tool versus alternatives like 'list_processes' or other system monitoring tools. It provides technical prerequisites (username required if host provided) but lacks strategic guidance on tool selection.

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