OpenWRT SSH MCP Server

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

No annotations are provided, so the description carries full burden. It states the tool enables the commissioner and mentions the passphrase usage, but doesn't disclose critical behavioral traits like whether this is a read-only or destructive operation, permission requirements, network impact, or error conditions. For a network configuration tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 two concise sentences that efficiently convey the tool's purpose and parameter context without wasted words. It's front-loaded with the main action and purpose, making it easy to scan and understand quickly.

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 no annotations, no output schema, and a network configuration tool that likely has side effects, the description is incomplete. It doesn't cover what happens after enabling (e.g., commissioner duration, how to disable), error handling, or return values. For a tool that modifies network state, more context about behavior and outcomes is needed.

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% with one optional parameter documented in the schema. The description adds minimal value beyond the schema by mentioning 'provided passphrase' but doesn't explain parameter semantics like passphrase format constraints or security implications. With high schema coverage, baseline 3 is appropriate as the description doesn't significantly enhance parameter understanding.

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 action ('Enable Thread Commissioner') and the purpose ('to allow new devices to join the network'), with additional context about how devices join. It distinguishes from siblings like 'openwrt_thread_create_network' by focusing on enabling commissioner functionality rather than creating the network itself. However, it doesn't explicitly contrast with all sibling tools, keeping it at 4 instead of 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?

The description implies usage when new devices need to join the Thread network, but doesn't provide explicit guidance on when to use this vs. alternatives like 'openwrt_thread_create_network' or prerequisites. It mentions the passphrase parameter context, which hints at usage, but lacks clear when-not-to-use scenarios or comparison to siblings.

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