Single tool with adequate naming (verb_noun: flipperzero_app_start) and reasonable description (58 chars). Input schema present with two parameters, both typed (string) and described. However, output schema is completely undocumented, no return type specification visible. Parameter descriptions are minimal (18-28 chars each), below the 72-char baseline. No error handling guidance, no recovery paths, no examples of valid app names. Tool lacks idempotency documentation and no mention of side effects despite WRITE risk classification. Missing pagination, structured output format, and field-level documentation.

• Document the complete output schema: return type (success/failure), app state, output/logs, exit code. Example: {"status": "running|exited", "output": "...", "exit_code": 0}
• Expand parameter descriptions to 50-100 chars with format constraints. For 'name': 'Flipper app name (case-sensitive, e.g. Infrared, GPIO, U2F). Call list_flipper_apps() to discover available apps.' For 'args': 'Optional command-line arguments passed to the app (string, max 256 chars).'
• Add error handling guidance: 'Returns error if app not found, Flipper disconnected, or app crashes. Check connection and app name validity before retrying.'
• Implement enum or discovery tool for valid app names. Either hardcode known Flipper apps (Infrared, GPIO, U2F, etc.) as an enum, or add a list_flipper_apps() tool.
• Clarify idempotency and side effects: 'Calling twice with same args will start the app twice (not idempotent). Use with caution in retry loops.'