flipper_cli_stream

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

The description discloses the core behavioral traits: it runs for a fixed duration, sends Ctrl+C, and returns printed output. This is sufficient given no annotations are present. It could add details about timeout limits or stderr handling, but the main behavior is transparent.

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 long: the first states the core function, the second provides usage examples. Every word earns its place, and information is front-loaded.

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 tool with two parameters and an output schema, the description covers the essential aspects: purpose, behavior, and example commands. It doesn't specify edge cases like what happens if the command exits early, but the description is sufficiently complete for selection and invocation.

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?

With schema description coverage at 0%, the description compensates by defining 'command' as a streaming CLI command and offering examples that show the expected format. 'seconds' is implied as the 'fixed duration', and the schema shows its default. The description adds meaningful context beyond the raw 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's function: 'Run a streaming CLI command for a fixed duration, then stop it (Ctrl+C) and return what it printed.' It uses a specific verb and resource, and distinguishes itself from sibling tools like flipper_cli by focusing on streaming commands interrupted after a duration.

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?

Explicitly states when to use this tool: 'Use for commands that stream until interrupted' and provides concrete examples like 'log', 'subghz rx 433920000 0', 'ir rx', 'input dump'. This clearly signals the intended use case and implies alternatives like flipper_cli for non-streaming commands.

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