Sets vibration intensity for DK-META2 devices via local BLE. Non-zero levels require confirm=true to ensure safe operation.
设置 DK-META2 振动强度；非零值必须 confirm=true。
| Name | Required | Description | Default |
|---|---|---|---|
| level | Yes | ||
| confirm | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It mentions that non-zero values require confirm=true, which is a useful behavioral hint, but it lacks information about permissions, side effects, reversibility, or response format. For a mutation tool, 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?
The description is a single, front-loaded sentence that is concise and directly states the action and a key condition. It doesn't waste words, though it could benefit from additional structure for clarity.
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 is a mutation with no annotations, 0% schema coverage, and an output schema that is not leveraged in the description, the definition is incomplete. It should describe parameter ranges, device state requirements, and side effects to be fully callable by an agent.
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 0%, meaning neither the schema nor the description explains the 'level' parameter (e.g., range, units) or the 'confirm' parameter beyond the conditional requirement. The description adds a constraint (confirm=true for non-zero) but leaves the primary parameter undefined.
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 ('设置' = set) and resource (DK-META2 vibration intensity). However, it doesn't clearly distinguish this tool from siblings like set_linear or set_rotary beyond the 'vibration' aspect. It's somewhat vague on whether this is the only vibration parameter tool.
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 a conditional rule about 'confirm' but does not explain when to use this tool versus alternatives, prerequisites, or device connection requirements. No when-to-use or when-not-to-use guidance is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.