From a0d2ed99fb195d509ccad91832c3b08c485fdfcc Mon Sep 17 00:00:00 2001 From: Michael Panchenko Date: Mon, 23 Feb 2026 19:37:42 +0100 Subject: [PATCH] Docstring: highlighted possibility to analyze dependencies with JBFindSymbol Models tend to not understand this until instructed, instead resorting to their internal much less efficient tools by default. --- src/serena/tools/jetbrains_tools.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/serena/tools/jetbrains_tools.py b/src/serena/tools/jetbrains_tools.py index 8ec84a07..119a5b5f 100644 --- a/src/serena/tools/jetbrains_tools.py +++ b/src/serena/tools/jetbrains_tools.py @@ -28,6 +28,8 @@ class JetBrainsFindSymbolTool(Tool, ToolMarkerSymbolicRead, ToolMarkerOptional): Retrieves information on all symbols/code entities (classes, methods, etc.) based on the given name path pattern. The returned symbol information can be used for edits or further queries. Specify `depth > 0` to retrieve children (e.g., methods of a class). + Important: through `search_deps=True` dependencies can be searched, which + should be preferred to web search or other less sophisticated approaches to analyzing dependencies. A name path is a path in the symbol tree *within a source file*. For example, the method `my_method` defined in class `MyClass` would have the name path `MyClass/my_method`.