flipper_deploy_fap

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

Discloses key behaviors: upload, md5 verification, and launching. Annotations (readOnlyHint=false, destructiveHint=false) are basic; description adds the verification step not evident from schema. Does not cover failure modes or permissions needed.

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?

Two sentences, no unnecessary words. Front-loaded with primary action and purpose. Efficiently communicates the tool's role.

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 development loop tool with 5 parameters and no output schema, the description covers core behavior and use case. Lacks details on prerequisites, error handling, or output expectations, but sufficient for typical usage.

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 description coverage is 80%; baseline is 3. Description adds overall workflow context but does not elaborate on individual parameters beyond what schema provides. No parameter details are missing, but no extra value added.

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?

Description clearly states specific actions: upload, verify by md5, launch a .fap file. It distinguishes from siblings like flipper_upload (upload only) and flipper_launch_app (launch only) by combining all three steps for a development workflow.

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?

Describes the tool as 'standard inner loop for Flipper app development' and suggests using it with a 'freshly built .fap'. Provides clear context but lacks explicit when-not-to-use or alternatives (e.g., flipper_upload for upload-only, flipper_launch_app for launch-only).

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