openwrt_execute_command

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 effectively communicates critical behavioral traits: the command validation against a security whitelist (important safety context), the execution nature (implies mutation/action), and the general-purpose nature. However, it doesn't mention potential side effects, error handling, or output format details.

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 perfectly concise with two sentences that each earn their place: the first establishes core functionality and security constraints, the second provides crucial usage guidance. No wasted words, and the most important information (what it does and when to use it) is front-loaded.

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 single-parameter tool with no annotations and no output schema, the description does well by covering purpose, security constraints, and usage guidelines. However, it lacks information about what the tool returns (output format) and doesn't mention potential risks or limitations of command execution, which would be valuable given the tool's power and potential for destructive operations.

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 the single parameter 'command' well-documented in the schema. The description adds only minimal value beyond the schema by reinforcing the whitelist requirement ('must be in whitelist' vs 'must be in whitelist' in schema). This meets the baseline expectation when schema coverage is complete.

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 ('execute a validated shell command') and resource ('on the OpenWRT router'), distinguishing it from sibling tools that perform specialized operations like getting firewall rules or system info. It explicitly mentions the security validation aspect, which adds important context.

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 provides explicit guidance on when to use this tool ('for commands not covered by other specialized tools'), creating a clear boundary with sibling tools that handle specific functions like opkg operations, thread management, or status retrieval. This helps the agent understand this is a general-purpose tool when specialized alternatives aren't available.

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