A recommendation request can be useful with partial context if you label the gaps. State the task, must-have requirements, budget or effort limit, environment, and the decision you need to make. Then distinguish confirmed facts from assumptions.
For example: “I need to annotate PDFs on a tablet, offline if possible; I do not yet know whether the files have forms.” That lets others suggest options and identify the missing test. Avoid implying that a feature is required when you have not verified the workflow.
Follow up after testing the critical unknown.