dsh-tool-search

LIMITATIONS

Known limitations

- **Native Tool Mode only.** Calls nested under `run_code` fail loud; Code Mode needs a separate SDK/search transport contract. - **Lexical search only.** Exact names, name boosts, descriptions, and BM25 achieve 100% recall for exact name @1 and representative capability queries @5 in the keyless scale benchmark; this small fixed corpus does not represent ambiguous queries, multilingual queries, or real model-use quality. Embeddings and provider-native search remain deferred. - **Global tools only.** Agent-scoped tools are already visible and never enter the deferred catalog. MCP resources and prompts are outside the tool registry and need their own consumer seams. - **Conservative late-tool policy.** Any restricted initial global view freezes the eligible-name set, so a harmless later registration may stay undiscoverable unless `alwaysVisible` names it. - **No namespace grouping.** Individual tool names remain the selection unit; large MCP servers may need a namespace-level result and load operation. - **No real provider cache benchmark.** Current token counts use the repository's fixed character estimate, and KV Cache compares only structural prefixes; no real tokenizer, bill, cache bucket, or end-to-end latency was measured. - **Private Git distribution.** The package is not published to a registry; installation requires authorized GitHub access, pnpm `11.7.0`, a reviewed commit, and a compatible DSH profile.