feat: standardize tool names by pod domain action

README.md

@@ -535,7 +535,7 @@ src/main/resources/
 
 ```java
 @McpFunction(
-    name = "sample.claim.search.resource",
+    name = "oth.cmm.claim.search",
     inputSchemaResource = "classpath:tool-schemas/cmm/claim-search-resource-input-schema.json",
     outputSchemaResource = "classpath:tool-schemas/cmm/claim-search-resource-output-schema.json"
 )
@@ -570,3 +570,21 @@ Tool 실행이 끝나면 아래 로그는 Schema 정의가 아니라 **검증을
 ```powershell
 .\gradlew.bat :dap-tool-oth:test --tests "io.shinhanlife.dap.mcc.biz.cmm.dto.ClaimSearchRequestSchemaTest"
 ```
+
+### Tool Naming Convention
+
+All Tool names use the four-level lowercase format `pod.domain.service.action`. Do not use underscores or CamelCase; use a hyphen (`-`) only when a single level has multiple words.
+
+- `pod`: deployment Tool Pod/module (`dap-tool-oth` → `oth`, `dap-tool-sms` → `sms`)
+- `domain`: business-domain package (`cmm`, `smp`, `sol`, etc.)
+- `service`: business service or resource
+- `action`: the requested operation (`search`, `list`, `detail`, `issue`, `inquiry`, etc.)
+
+```text
+oth.cmm.bond.issue
+oth.cmm.claim.search
+oth.sol.request.list
+oth.smp.weather.inquiry
+```
+
+When Scaffold receives `dap-tool-oth`, `cmm`, and `ClaimSearch`, it generates `oth.cmm.claim.search`. The `validateMcpToolNames` Gradle task rejects both a duplicate name and any name outside this format before packaging, including its source file and line number.