Standardize the nav bar (#359)

 - Use index.md files where a section has an overview
 - Except for section-headers, as that just looks weird
 - Also reformatted some code blocks for syntax highlighting

---------

Co-authored-by: Mackenzie Zastrow <zastrowm@users.noreply.github.com>

Author: zastrowm

AGENTS.md

@@ -193,13 +193,13 @@ The goal of this repository is to revamp this documentation repo so that it prov
 │       │   ├── streaming
 │       │   │   ├── async-iterators.md
 │       │   │   ├── callback-handlers.md
-│       │   │   └── overview.md
+│       │   │   └── index.md
 │       │   └── tools
 │       │       ├── community-tools-package.md
 │       │       ├── executors.md
 │       │       ├── mcp-tools.md
 │       │       ├── python-tools.md
-│       │       └── tools_overview.md
+│       │       └── index.md
 │       ├── deploy
 │       │   ├── deploy_to_amazon_ec2.md
 │       │   ├── deploy_to_amazon_eks.md

docs/user-guide/concepts/agents/agent-loop.md

@@ -110,7 +110,7 @@ Solutions:
 
 ### Inappropriate Tool Selection
 
-When the model consistently picks the wrong tool, the problem is usually ambiguous tool descriptions. Review the descriptions from the model's perspective. If two tools have overlapping descriptions, the model has no basis for choosing between them. See [Tools Overview](../tools/tools_overview.md) for guidance on writing effective descriptions.
+When the model consistently picks the wrong tool, the problem is usually ambiguous tool descriptions. Review the descriptions from the model's perspective. If two tools have overlapping descriptions, the model has no basis for choosing between them. See [Tools Overview](../tools/index.md) for guidance on writing effective descriptions.
 
 ### MaxTokensReachedException
 

docs/user-guide/concepts/experimental/bidirectional-streaming/agent.md

@@ -233,7 +233,7 @@ See [Model Providers](models/nova_sonic.md) for provider-specific options.
 
 `BidiAgent` supports many of the same constructs as `Agent`:
 
-- **[Tools](../../tools/tools_overview.md)**: Function calling works identically
+- **[Tools](../../tools/index.md)**: Function calling works identically
 - **[Hooks](hooks.md)**: Lifecycle event handling with bidirectional-specific events
 - **[Session Management](session-management.md)**: Conversation persistence across sessions
 - **[Tool Executors](../../tools/executors.md)**: Concurrent and custom execution patterns

docs/user-guide/concepts/experimental/bidirectional-streaming/events.md

@@ -6,7 +6,7 @@ Bidirectional streaming events enable real-time monitoring and processing of aud
 
 ## Event Model
 
-Bidirectional streaming uses a different event model than [standard streaming](../../streaming/overview.md):
+Bidirectional streaming uses a different event model than [standard streaming](../../streaming/index.md):
 
 **Standard Streaming:**
 
@@ -322,7 +322,7 @@ Events for tool execution during conversations. Bidirectional streaming reuses t
 
 #### ToolUseStreamEvent
 
-Emitted when the model requests tool execution. See [Tools Overview](../../tools/tools_overview.md) for details.
+Emitted when the model requests tool execution. See [Tools Overview](../../tools/index.md) for details.
 
 ```python
 {

docs/user-guide/concepts/interrupts.md

@@ -156,7 +156,7 @@ agent = Agent(
 
 ```
 
-> ⚠️ Interrupts are not supported in [direct tool calls](./tools/tools_overview.md#direct-method-calls) (i.e., calls such as `agent.tool.my_tool()`).
+> ⚠️ Interrupts are not supported in [direct tool calls](./tools/index.md#direct-method-calls) (i.e., calls such as `agent.tool.my_tool()`).
 
 ### Components
 

docs/user-guide/concepts/multi-agent/graph.md

@@ -334,7 +334,7 @@ async for event in graph.stream_async("Research and analyze market trends"):
         print(f"Graph completed: {result.status}")
 ```
 
-See the [streaming overview](../streaming/overview.md#multi-agent-events) for details on all multi-agent event types.
+See the [streaming overview](../streaming/index.md#multi-agent-events) for details on all multi-agent event types.
 
 ## Graph Results
 

docs/user-guide/concepts/multi-agent/swarm.md

@@ -225,7 +225,7 @@ async for event in swarm.stream_async("Design and implement a REST API"):
         print(f"\nSwarm completed: {result.status}")
 ```
 
-See the [streaming overview](../streaming/overview.md#multi-agent-events) for details on all multi-agent event types.
+See the [streaming overview](../streaming/index.md#multi-agent-events) for details on all multi-agent event types.
 
 ## Swarm Results
 

docs/user-guide/concepts/streaming/async-iterators.md

@@ -2,7 +2,7 @@
 
 Async iterators provide asynchronous streaming of agent events, allowing you to process events as they occur in real-time. This approach is ideal for asynchronous frameworks where you need fine-grained control over async execution flow.
 
-For a complete list of available events including text generation, tool usage, lifecycle, and reasoning events, see the [streaming overview](./overview.md#event-types).
+For a complete list of available events including text generation, tool usage, lifecycle, and reasoning events, see the [streaming overview](./index.md#event-types).
 
 ## Basic Usage
 

docs/user-guide/concepts/streaming/callback-handlers.md

@@ -4,7 +4,7 @@
 
 Callback handlers allow you to intercept and process events as they happen during agent execution in Python. This enables real-time monitoring, custom output formatting, and integration with external systems through function-based event handling.
 
-For a complete list of available events including text generation, tool usage, lifecycle, and reasoning events, see the [streaming overview](./overview.md#event-types).
+For a complete list of available events including text generation, tool usage, lifecycle, and reasoning events, see the [streaming overview](./index.md#event-types).
 
 > **Note:** For asynchronous applications, consider [async iterators](./async-iterators.md) instead.