fix(mcp): set hasMore on size-cap trim, fix tools.json wording

Author: Shreyansh100704

openmetadata-mcp/src/main/java/org/openmetadata/mcp/tools/SearchMetadataTool.java

@@ -334,7 +334,7 @@ static Map<String, Object> buildEnhancedSearchResponse(
           "message",
           String.format(
               "Found %d total results, showing first %d. "
-                  + "There are many matching assets — are you looking for something specific? "
+                  + "There are many matching assets. Are you looking for something specific?"
                   + "Try narrowing with a service name, schema name, or more specific search term.",
               totalResults, cleanedResults.size()));
       result.put("hasMore", true);
@@ -362,11 +362,12 @@ static Map<String, Object> buildEnhancedSearchResponse(
             cleanedResults.size());
         result.put("results", trimmed);
         result.put("returnedCount", trimmed.size());
+        result.put("hasMore", true);
         result.put(
             "message",
             String.format(
                 "Response exceeded %d characters and was trimmed to %d of %d results. "
-                    + "There are many matching assets — are you looking for something specific? "
+                    + "There are many matching assets. Are you looking for something specific?"
                     + "Try narrowing with a service name, schema, or specific name.",
                 MAX_RESPONSE_CHARS, trimmed.size(), totalResults));
       }

openmetadata-mcp/src/main/resources/json/data/mcp/tools.json

@@ -26,7 +26,7 @@
           },
           "size": {
             "type": "integer",
-            "description": "Number of results to return. Default is 10. For broad or generic queries (e.g. 'show all tables'), keep size small (5-10) so each result includes complete information. Only increase size when the query is specific enough that results will be narrow and focused. Maximum allowed is 50.",
+            "description": "Number of results to return. Default is 10. For broad or generic queries (e.g. 'show all tables'), keep size small (5-10), as results are summaries; use get_entity_details for full entity info. Only increase size when the query is specific enough that results will be narrow and focused. Maximum allowed is 50.",
             "default": 10
           },
           "includeDeleted": {