further prompt refinement, discourage use of temp ids and encourage getting the widget tree often (#249)

Author: jakemac53

pkgs/dart_mcp_server/lib/src/mixins/dtd.dart

@@ -662,10 +662,11 @@ base mixin DartToolingDaemonSupport
       additionalProperties: true,
       description:
           'Command arguments are passed as additional properties to this map.'
-          'To specify a widgets, you should first use the '
-          '"${getWidgetTreeTool.name}" tool to inspect the widget tree for the '
-          'value id of the widget and then use the "ByValueKey" finder type '
-          'with that id.',
+          'To specify a widget to interact with, you must first use the '
+          '"${getWidgetTreeTool.name}" tool to get the widget tree of the '
+          'current page so that you can see the available widgets. Do not '
+          'guess at how to select widgets, use the real text, tooltips, and '
+          'widget types that you see present in the tree.',
       properties: {
         'command': Schema.string(
           // Commented out values are flutter_driver commands that are not
@@ -706,7 +707,7 @@ base mixin DartToolingDaemonSupport
         'duration': Schema.string(
           description:
               'Required for the scroll command, the duration of the '
-              'scrolling action in microseconds as a stringified integer.',
+              'scrolling action in MICROSECONDS as a stringified integer.',
         ),
         'dx': Schema.string(
           description:

pkgs/dart_mcp_server/lib/src/mixins/prompts.dart

@@ -68,6 +68,8 @@ Perform the following tasks in order:
   widgets, but instead select them based on text, type, tooltip, etc. Avoid
   reading in files to accomplish this task, just inspect the live state of the
   app and widget tree. If you get stuck, feel free to ask the user for help.
+  ALWAYS get the widget tree after performing any interaction, so you can see
+  the updated state of the app.
 - If you are able to successfully complete the journey, then create a flutter
   driver based test with an appropriate name under the integration_test
   directory. The test should perform all the successful actions that you