Discover Gradle projects

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint annotation declares this as a safe read operation, and the description adds the exact behavior of looking for directories with settings.gradle[.kts]. It doesn't contradict the annotation and provides useful context about the search criterion and downstream usage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is exactly two sentences: the first defines the tool's purpose precisely, and the second gives actionable guidance. Every word earns its place, with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only discovery tool with two parameters and no output schema, the description conveys the search mechanism, the criterion, and a practical use case. It doesn't describe the return format, but the guidance is sufficient for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage for both searchPath and maxDepth, so the baseline is 3. The description adds little parameter-specific detail beyond what the schema already provides, though it reinforces the path-based nature of the search.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Find' and the resource 'Android/Gradle projects' with a precise identifying criterion: directories containing settings.gradle[.kts]. It distinguishes itself from sibling tools like build_app or list_modules by focusing on project discovery.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly tells the agent to use the result with session_set_defaults projectDir, providing a concrete use case. It doesn't mention when not to use it or alternatives, but among the siblings there is no other discovery tool, so the guidance is reasonably clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.