OpenWRT SSH MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a read operation ('Get') but lacks details on permissions required, rate limits, error conditions, or the format/structure of the returned information. For a tool with no annotation coverage, this is a significant gap in transparency.

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, efficient sentence that front-loads the core purpose and then enumerates specific data points. Every word contributes to clarity without redundancy, making it appropriately sized and well-structured for quick comprehension.

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 complexity (retrieving multiple network details), lack of annotations, and absence of an output schema, the description is minimally adequate. It specifies what information is gathered but does not address behavioral aspects like response format or operational constraints, leaving gaps for the agent to handle.

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 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description appropriately adds no parameter information, as none are needed, aligning with the baseline expectation for zero-parameter tools.

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 specific action ('Get comprehensive Thread network information') and lists the detailed resources included (state, channel, PAN ID, network name, IP addresses, neighbors, children). It effectively distinguishes this tool from siblings like 'openwrt_thread_get_state' by specifying a broader scope of information beyond just state.

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 for retrieving Thread network data but provides no explicit guidance on when to use this tool versus alternatives like 'openwrt_thread_get_state' or 'openwrt_thread_get_dataset'. No exclusions or prerequisites are mentioned, leaving the agent to infer context from the tool name and listed data points.

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