AWS docs search. Each result's `context` is verbatim page text -- a real chunk of the actual page, not a short snippet -- and usually already contains the answer, so answer directly from it. Use `read_documentation` only when the chunks genuinely lack the needed detail.
Pick ONE topic. Add a 2nd ONLY if query genuinely spans domains. Extra topics dilute ranking.
- reference_documentation -- API/SDK/CLI specs, config params
- current_awareness -- new/released/announced
- troubleshooting -- errors, "how to fix" (NOT for conceptual/feature questions)
- amplify_docs -- Amplify (+ language)
- cdk_docs -- CDK concepts/guides
- cdk_constructs -- CDK code samples, L3
- cloudformation -- CFN/SAM templates
- strands_docs -- Strands Agents SDK (its Skills/agents concepts go here, NOT agent_skills)
- agent_skills -- this tool's guided skills (load via `retrieve_skill`)
- general (default) -- architecture, best practices, tutorials, feature behavior
Results: rank_order (lower=better), url, title, context (verbatim page chunk -- answer directly from it).
Connector