Vibrate

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

No annotations are provided, so the description must carry the burden. It states 'Forwards a command to physical hardware', implying interaction with hardware but lacks details on side effects, permissions needed, or potential damage. Minimal behavioral insight.

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?

Two short sentences conveying purpose without redundancy. The '[Hardware control]' prefix adds minimal value but does not detract. Could be slightly more streamlined.

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?

Tool has three parameters and no output schema, yet the description omits return behavior, error conditions, or hardware constraints. Given complexity, more context (e.g., that intensity is relative, or what happens on invalid device) 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%, so parameters are already documented. The description adds 'Set vibration intensity', aligning with the intensity parameter, but does not clarify the 'actuator_index' parameter beyond the schema.

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 ('vibration intensity on a device'), clearly identifying the tool's function. It distinguishes from sibling tools like 'oscillate', 'rotate', and 'vibrate_pattern' by focusing on intensity setting.

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?

No guidance on when to use this tool versus alternatives such as 'oscillate', 'rotate', or 'vibrate_pattern'. There are no exclusions or context about prerequisites (e.g., device must be connected).

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