Answer: To optimize tool discovery, use descriptive tool names and descriptions with specific keywords, and add a system prompt section listing available tool categories via the `systemPrompt` option (TypeScript) or `system_prompt` (Python), using the `claude_code` preset with `append`. Status: Confirmed Entry: tool/claude-code/agents-and-automation/optimize-tool-discovery Revision: 1 Digest: sha256:4df99be58dc61dda (changes whenever the content changes) Timeline: Created: 2026-11-13T03:03:05Z Last changed: 2026-11-13T03:03:05Z Last verified: 2026-11-20T12:17:34Z Next check: 2026-11-21T12:17:34Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Naming guidance | search_slack_messages | [1] | 2026-11-20 Description guidance | Search Slack messages by keyword, channel, or date range | [1] | 2026-11-20 TypeScript option | systemPrompt | [1] | 2026-11-20 Python option | system_prompt | [1] | 2026-11-20 Preset | claude_code | [1] | 2026-11-20 Sources: [1] Anthropic. "Scale to many tools with tool search". https://code.claude.com/docs/en/agent-sdk/tool-search.md Role: primary. Accessed: 2026-11-20T12:17:34Z Quote: "Names like `search_slack_messages` surface for a wider range of requests than `query_slack`." (Supports: Naming guidance) Quote: "Descriptions with specific keywords ("Search Slack messages by keyword, channel, or date range") match more queries than generic ones ("Query Slack")." (Supports: Description guidance) Quote: "Pass the text in the `systemPrompt` option of `query()` in TypeScript, or `system_prompt` in Python." (Supports: TypeScript option, Python option) Quote: "Use the `claude_code` preset with `append`, which adds your text to the preset's prompt instead of replacing it:" (Supports: Preset) Published: 2026-11-20T03:17:50Z Snapshot SHA-256: 53192262923b7b10fe3d4ebcd036e818b6389d51f1e5e491e6febaf5ee31f153 (captured 2026-11-13T03:03:04Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:03:05Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:17:34Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:17:34Z Last attempt: 2026-11-20T12:17:34Z Notes and limitations: Extracted automatically from a single official source (section "Optimize tool discovery"). Related: https://latestn.com/tool/claude-code/agents-and-automation/optional-tool-parameter How do I make a parameter optional in a Claude Code custom tool? https://latestn.com/tool/claude-code/agents-and-automation/output-format-configuration How do I configure the output format for a Claude Code agent? https://latestn.com/tool/claude-code/agents-and-automation/parallel-agent-approaches What are the different ways Claude Code can run multiple tasks in parallel? https://latestn.com/tool/claude-code/agents-and-automation/multiple-plugin-sources How do I load plugins from multiple sources in the Claude Code Agent SDK? https://latestn.com/tool/claude-code/agents-and-automation/open-agent-view-by-default How do I open Claude Code's agent view by default? https://latestn.com/tool/claude-code/agents-and-automation/opt-in-task-tracking-tools How do I opt in to Claude Code's task-tracking tools on models where they aren't available by default? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:03:05Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/agents-and-automation/optimize-tool-discovery/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/agents-and-automation/optimize-tool-discovery POST: https://latestn.com/dispute/tool/claude-code/agents-and-automation/optimize-tool-discovery with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/agents-and-automation/optimize-tool-discovery?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How can I optimize tool discovery for tool search in Claude Code? Revision 1, last verified 2026-11-20T12:17:34Z. https://latestn.com/tool/claude-code/agents-and-automation/optimize-tool-discovery (accessed 2026-11-21T09:58:24Z). @misc{LatestN_tool_claude_code_agents_and_automation_optimize_tool_discovery_r1, title = {How can I optimize tool discovery for tool search in Claude Code?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/agents-and-automation/optimize-tool-discovery}}, note = {Revision 1; digest sha256:4df99be58dc61dda; last verified 2026-11-20T12:17:34Z; accessed 2026-11-21T09:58:24Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/agents-and-automation/optimize-tool-discovery