flipper_rename

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

Annotations indicate mutating but not destructive. The description adds no additional behavioral context, such as overwriting behavior, atomicity, or edge cases, beyond stating the action.

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 a single sentence that is front-loaded and concise. Every word is essential.

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?

Without an output schema, the description should explain return behavior (e.g., success status). It omits details on whether rename is atomic, whether it works on directories, or behavior when new_path exists. For a mutation tool with many siblings, it is under-informative.

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 only 33% (port described). The description does not clarify the format or constraints of old_path and new_path (e.g., absolute vs relative, must be on same filesystem). It provides minimal added meaning beyond parameter names.

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 renames or moves a file or directory on the device. It uses specific verbs and a clear resource, distinguishing it from siblings like flipper_delete or flipper_upload.

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 no guidance on when to use this tool versus alternatives. No explicit conditions, prerequisites, or when-not-to-use information is given.

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