qflipper_backup

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, meaning the tool writes data but is not destructive. The description adds valuable behavioral context: it releases the serial port before backing up. This goes beyond the annotations and clarifies the tool's impact on device connectivity.

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, front-loaded with the primary action, and contains no filler. Every sentence provides essential information: the action and a key behavioral side effect.

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 tool's complexity (a backup operation) and the lack of an output schema, the description is somewhat sparse. It does not explain return values, success/failure indications, or whether existing files are overwritten. However, for a backup tool with clear input parameters, it covers the essential purpose and a critical side effect.

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 coverage is 50% (only local_path has a description). The description does not elaborate on either parameter, leaving the 'timeout' parameter entirely undocumented beyond its schema definition. The description adds no value beyond the schema for parameter understanding.

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 backs up the device's internal memory to a host directory using qFlipper-cli, with the specific verb 'back up' and the resource 'device's internal memory'. It distinguishes from sibling tools like flipper_upload or flipper_download, which handle file transfers, not full memory backup.

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 mentions 'Releases the serial port first,' giving a practical usage detail, but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusion criteria or prerequisites. The context is implied but not thorough.

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