clean_firmware_filesDeletes downloaded firmware files from an iKuai router to free storage; set confirm to true to execute the cleanup.
清理已下载的固件文件
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | No | 必须设为 True 才会执行 |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Clean' implies deletion of files, but the description never states what is removed, whether the action is reversible, whether it affects the active firmware image, or what permissions are needed. For a destructive operation this is a significant gap.
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?
A single short phrase that is front-loaded and free of waste. It is efficient, though the extreme brevity leaves it under-specified rather than genuinely concise.
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?
An output schema exists so return values need not be explained, but for a deletion tool with zero annotation coverage the description should disclose destructiveness, scope, and safety prerequisites. It leaves an agent without enough context to invoke it safely.
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?
There is a single parameter with 100% schema description coverage, so the schema already documents the confirm flag and its default. The description adds no meaning beyond the schema, making the baseline of 3 appropriate.
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 states a specific verb+resource ('clean downloaded firmware files'), so an agent can tell what the tool does. However, it offers no differentiation from the many firmware-related siblings such as get_firmware_version, check_firmware_update, and start_firmware_upgrade.
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?
There is no guidance on when to use this tool, no prerequisites, and no mention of alternatives. The agent gets a purpose statement but nothing about the conditions that should trigger cleanup.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.