flipper_save_script

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

Annotations indicate the tool is not read-only (write operation) and not destructive. The description adds the destination and purpose but does not disclose whether existing files are overwritten or if directories are created. This leaves ambiguity for the agent.

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?

Single sentence, no wasted words. Information is front-loaded. However, slightly more detail (e.g., overwrite behavior) could be added without harming conciseness.

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 mutation tool with three parameters and no output schema, the description is incomplete. Missing: what 'source' is, how 'port' is used, and behavior on existing files. The agent cannot reliably invoke this tool based on the description alone.

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 33% (only 'port' described). The description does not explain 'name' (e.g., file name extension?) or 'source' (content or file path?), which are critical. This fails to compensate for low schema coverage.

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 verb 'Save', the resource 'JavaScript file', the destination path '/ext/apps/Scripts', and the purpose (runnable from Apps > Scripts menu). This distinguishes it from sibling tools like flipper_upload or flipper_write_file.

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 implies usage for saving scripts to the Scripts folder but does not explicitly state when to use this tool versus alternatives (e.g., flipper_write_file, flipper_upload). No 'when not to use' guidance is provided.

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