flipper_input_sequence

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

Annotations indicate non-destructive and non-read-only behavior, but the description adds that it sends button presses and can capture a screenshot. It does not elaborate on potential side effects like device state changes or connectivity requirements, which are beyond the annotation hints.

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 sentences: the first explains what the tool does, the second gives a concrete use case. No unnecessary words, highly efficient.

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 absence of an output schema and the simplicity of the tool, the description covers the essential behavior and use case adequately. It could mention the return value (screenshot or success) but is otherwise complete enough for an agent to understand.

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 75%, and the tool description's mention of 'screenshot' corresponds to the boolean parameter. However, the description does not add significant detail beyond the schema's own parameter descriptions for keys, port, and delay. The value added is contextual framing.

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 multiple button presses in order and optionally returns a screenshot. It distinguishes itself from sibling tools like flipper_input (single press) and flipper_screenshot (just screenshot) by specifying the combined action.

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 clear use case: 'Use this to navigate to a screen and see the result in one call.' This implies when to use it, but does not explicitly state when not to use it or mention alternatives. However, the context of sibling tools makes it sufficient.

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