/** * One-line prompt hints for each tool, shown in the system prompt's Tools * section. Full parameter docs live on each tool's JSON schema description * (sent separately via the tool definition), so these hints stay short. * * Hints exist ONLY for tools whose correct usage is NOT obvious from their * schema description alone. The core file/nav/exec tools (read/write/edit/ * bash/find/grep/ls) deliberately have NO hint: an ablation (experiments/ * prompt-bench, Opus n=12) showed dropping their hints did not change tool * selection — the schema description already carries when/how to use them. * Cross-tool preferences for those tools live in TOOL_STEERING instead. */ export declare const TOOL_PROMPT_HINTS: Record; /** * Cross-tool selection guidance that no single tool's own schema description * can state (it's relational). Each clause only renders when its tools are * actually active, so the line never references an unavailable tool. Proven * equivalent to the full per-tool hint list in the prompt-bench ablation * while costing ~95% fewer words. */ export declare const TOOL_STEERING_CLAUSES: ReadonlyArray<{ needs: readonly string[]; text: string; }>; /** Build the steering line from whichever clauses apply to the active tools. */ export declare function buildToolSteering(activeTools: readonly string[]): string; /** * Every tool name `createTools()` can register, including the conditional ones * (web_search on non-Anthropic providers, generate_image with OpenAI auth, * plan tools, the subagent cluster) and `tool_search`, which MCP deferred * loading adds. Used to validate an agent definition's `tools:` frontmatter — * an unknown name is silently dropped by the session allow-list, so a typo * would otherwise cost the agent a capability with no signal at all. */ export declare const BUILTIN_TOOL_NAMES: readonly string[]; /** Tools always rendered when no explicit tool list is provided. */ export declare const DEFAULT_TOOL_NAMES: readonly string[]; //# sourceMappingURL=prompt-hints.d.ts.map