flipper_ir_universal

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

With no annotations, the description carries the full burden. It discloses only that it sends a signal, with no mention of side effects, prerequisites (e.g., connection), or failure behavior. The tip to use flipper_cli for listing signals is useful but does not compensate for missing behavioral 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 two sentences, front-loaded with the core action, and every word earns its place. It includes parameter hints and a practical listing command without unnecessary fluff.

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 simple 2-parameter action tool, the description is adequate: it states what it does, explains both params, and offers a way to discover valid signals. Output schema exists so return values aren't needed. Minor gap: no mention of whether the IR blast requires line-of-sight or if the device must be connected, but these are not critical for a basic send action.

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?

The schema has 0% parameter descriptions, but the description adds rich meaning: it explains the 'remote' parameter with example values (tv, ac, audio, projector) and the 'signal' parameter with examples (Power, Vol_up, Mute), and provides a command to enumerate valid signals. This fully compensates for the empty 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 clearly states the tool sends a signal from a built-in universal IR remote, with a specific verb ('send') and resource ('built-in universal IR remote'). It distinguishes from the sibling flipper_ir_send by emphasizing 'built-in universal' and listing remote categories (tv, ac, audio, projector).

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 for sending universal IR signals but does not explicitly contrast with alternatives like flipper_ir_send. It does provide helpful usage guidance via the flipper_cli command to list signals, but lacks a clear 'when to use vs when not to use' statement.

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