flipper_upload

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

Discloses verification behavior and failure handling ('fails loudly'). Annotations already indicate non-readOnly and non-destructive, but description adds valuable behavioral context. Minor omission: does not mention the verify parameter default or toggle possibility.

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, clear and to the point. No unnecessary words.

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?

Minimally complete for a simple upload tool, but lacks details on return value, error format, and the interplay between parameters. With no output schema and low schema coverage, more detail would be helpful.

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 low (25%), and the description does not explicitly describe any parameter beyond implying local_path and device_path. No guidance on port, verify, or their semantics.

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?

Describes uploading a file and verifying by MD5, which is a specific action. However, it does not distinguish from similar tools like flipper_write_file or flipper_deploy_fap.

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 upload with verification but does not provide explicit when-to-use or alternative suggestions. Context is clear but not comprehensive.

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