flipper_cli

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

Annotations show non-destructive and non-read-only hints, which the description does not contradict. The description adds behavioral context by warning against streaming commands and automatic session management, but does not detail potential side effects of arbitrary CLI commands or return format, leaving some gaps.

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 compact with three sentences that immediately state purpose and then add caveats. There is no redundancy or unnecessary detail, making it efficient and 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?

With no output schema, the description vaguely says 'return its output' without specifying format or error behavior. It distinguishes well from 65+ siblings but lacks details on output structure and edge cases, making it less complete for a general CLI tool.

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?

Input schema has 100% coverage with descriptions for all three parameters (port, command, timeout). The description adds minimal extra meaning beyond the schema, such as suggesting 'run help' for command options. Baseline 3 is appropriate since the schema does the heavy lifting.

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 runs commands on the Flipper's CLI and returns output. It distinguishes itself as a general-purpose escape hatch and explicitly mentions what it does not cover (streaming commands like 'log'), setting it apart from siblings.

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 explicit guidance on when to use it (general-purpose escape hatch) and when not to (streaming commands, with a specific alternative 'flipper_log' named). It also notes that 'start_rpc_session' is managed automatically, giving clear usage context.

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