diff --git a/docs/core-concepts/Agents.md b/docs/core-concepts/Agents.md
index 9c37e5c6a..f4a5d950b 100644
--- a/docs/core-concepts/Agents.md
+++ b/docs/core-concepts/Agents.md
@@ -10,30 +10,31 @@ description: What are crewAI Agents and how to use them.
       <li class='leading-3'>Perform tasks</li>
       <li class='leading-3'>Make decisions</li>
       <li class='leading-3'>Communicate with other agents</li>
+    <ul>
       <br/>
     Think of an agent as a member of a team, with specific skills and a particular job to do. Agents can have different roles like 'Researcher', 'Writer', or 'Customer Support', each contributing to the overall goal of the crew.
 
 ## Agent Attributes
 
-| Attribute           | Description                          |
-| :------------------ | :----------------------------------- |
-| **Role**            | Defines the agent's function within the crew. It determines the kind of tasks the agent is best suited for.  |
-| **Goal**            | The individual objective that the agent aims to achieve. It guides the agent's decision-making process. |
-| **Backstory**       | Provides context to the agent's role and goal, enriching the interaction and collaboration dynamics. |
-| **LLM**             | The language model used by the agent to process and generate text. Defaults to using OpenAI's GPT-4 (`ChatOpenAI`), unless another model is specified through the environment variable "OPENAI_MODEL_NAME". |
-| **Tools**           | Set of capabilities or functions that the agent can use to perform tasks. Tools can be shared or exclusive to specific agents. It's an attribute that can be set during the initialization of an agent. |
-| **Function Calling LLM** | If passed this agent will use this LLM to do function calling for tools instead of relying on the main llm output |
-| **Max Iter**        | The maximum number of iterations the agent can perform before being forced to give its best answer. Default is `15`. |
-| **Max RPM**         | The maximum number of requests per minute the agent can perform to avoid rate limits. It's optional and can be left unspecified. |
-| **Verbose**         | Enables detailed logging of the agent's execution for debugging or monitoring purposes when set to True. Default is `False` |
-| **Allow Delegation**| Agents can delegate tasks or questions to one another, ensuring that each task is handled by the most suitable agent. |
-| **Step Callback**   | A function that is called after each step of the agent. This can be used to log the agent's actions or to perform other operations. It will overwrite the crew `step_callback`. |
-| **Memory**          | Indicates whether the agent should have memory or not, with a default value of False. This impacts the agent's ability to remember past interactions. Default is `False` |
+| Attribute              | Description                                                                                                                                                                                                                                    |
+| :--------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Role**               | Defines the agent's function within the crew. It determines the kind of tasks the agent is best suited for.                                                                                                                                    |
+| **Goal**               | The individual objective that the agent aims to achieve. It guides the agent's decision-making process.                                                                                                                                        |
+| **Backstory**          | Provides context to the agent's role and goal, enriching the interaction and collaboration dynamics.                                                                                                                                           |
+| **LLM** *(optional)*                 | The language model used by the agent to process and generate text. It dynamically fetches the model name from the `OPENAI_MODEL_NAME` environment variable, defaulting to "gpt-4" if not specified.                                            |
+| **Tools** *(optional)*               | Set of capabilities or functions that the agent can use to perform tasks. Tools can be shared or exclusive to specific agents. It's an attribute that can be set during the initialization of an agent, with a default value of an empty list.  |
+| **Function Calling LLM** *(optional)*  | If passed, this agent will use this LLM to execute function calling for tools instead of relying on the main LLM output.                                                                                                                       |
+| **Max Iter** *(optional)*            | The maximum number of iterations the agent can perform before being forced to give its best answer. Default is `15`.                                                                                                                           |
+| **Max RPM** *(optional)*             | The maximum number of requests per minute the agent can perform to avoid rate limits. It's optional and can be left unspecified, with a default value of `None`.                                                                               |
+| **Verbose** *(optional)*             | Enables detailed logging of the agent's execution for debugging or monitoring purposes when set to True. Default is `False`.                                                                                                                    |
+| **Allow Delegation** *(optional)*    | Agents can delegate tasks or questions to one another, ensuring that each task is handled by the most suitable agent. Default is `True`.                                                                                                       |
+| **Step Callback** *(optional)*       | A function that is called after each step of the agent. This can be used to log the agent's actions or to perform other operations. It will overwrite the crew `step_callback`.                                                                |
+| **Memory** *(optional)*             | Indicates whether the agent should have memory or not, with a default value of False. This impacts the agent's ability to remember past interactions. Default is `False`.                                                                      |
 
 ## Creating an Agent
 
 !!! note "Agent Interaction"
-    Agents can interact with each other using the CrewAI's built-in delegation and communication mechanisms.<br/>This allows for dynamic task management and problem-solving within the crew.
+    Agents can interact with each other using crewAI's built-in delegation and communication mechanisms. This allows for dynamic task management and problem-solving within the crew.
 
 To create an agent, you would typically initialize an instance of the `Agent` class with the desired properties. Here's a conceptual example including all attributes:
 
@@ -49,7 +50,7 @@ agent = Agent(
   to the business.
   You're currently working on a project to analyze the
   performance of our marketing campaigns.""",
-  tools=[my_tool1, my_tool2],  # Optional
+  tools=[my_tool1, my_tool2],  # Optional, defaults to an empty list
   llm=my_llm,  # Optional
   function_calling_llm=my_llm,  # Optional
   max_iter=15,  # Optional
diff --git a/docs/core-concepts/Collaboration.md b/docs/core-concepts/Collaboration.md
index 7950af034..ddc4f678b 100644
--- a/docs/core-concepts/Collaboration.md
+++ b/docs/core-concepts/Collaboration.md
@@ -1,3 +1,4 @@
+```markdown
 ---
 title: How Agents Collaborate in CrewAI
 description: Exploring the dynamics of agent collaboration within the CrewAI framework, focusing on the newly integrated features for enhanced functionality.
@@ -14,15 +15,16 @@ description: Exploring the dynamics of agent collaboration within the CrewAI fra
 ## Enhanced Attributes for Improved Collaboration
 The `Crew` class has been enriched with several attributes to support advanced functionalities:
 
-- **Language Model Management (`manager_llm`, `function_calling_llm`)**: Manages language models for executing tasks and tools, facilitating sophisticated agent-tool interactions.
+- **Language Model Management (`manager_llm`, `function_calling_llm`)**: Manages language models for executing tasks and tools, facilitating sophisticated agent-tool interactions. It's important to note that `manager_llm` is mandatory when using a hierarchical process for ensuring proper execution flow.
 - **Process Flow (`process`)**: Defines the execution logic (e.g., sequential, hierarchical) to streamline task distribution and execution.
-- **Verbose Logging (`verbose`)**: Offers detailed logging capabilities for monitoring and debugging purposes.
+- **Verbose Logging (`verbose`)**: Offers detailed logging capabilities for monitoring and debugging purposes. It supports both integer and boolean types to indicate the verbosity level.
 - **Configuration (`config`)**: Allows extensive customization to tailor the crew's behavior according to specific requirements.
 - **Rate Limiting (`max_rpm`)**: Ensures efficient utilization of resources by limiting requests per minute.
 - **Internationalization Support (`language`)**: Facilitates operation in multiple languages, enhancing global usability.
 - **Execution and Output Handling (`full_output`)**: Distinguishes between full and final outputs for nuanced control over task results.
 - **Callback and Telemetry (`step_callback`)**: Integrates callbacks for step-wise execution monitoring and telemetry for performance analytics.
-- **Crew Sharing (`share_crew`)**: Enables sharing of crew information with CrewAI for continuous improvement.
+- **Crew Sharing (`share_crew`)**: Enables sharing of crew information with CrewAI for continuous improvement and training models.
+- **Usage Metrics (`usage_metrics`)**: Store all metrics for the language model (LLM) usage during all tasks' execution, providing insights into operational efficiency and areas for improvement, you can check it after the crew execution.
 
 ## Delegation: Dividing to Conquer
 Delegation enhances functionality by allowing agents to intelligently assign tasks or seek help, thereby amplifying the crew's overall capability.
@@ -34,4 +36,4 @@ Setting up a crew involves defining the roles and capabilities of each agent. Cr
 Consider a crew with a researcher agent tasked with data gathering and a writer agent responsible for compiling reports. The integration of advanced language model management and process flow attributes allows for more sophisticated interactions, such as the writer delegating complex research tasks to the researcher or querying specific information, thereby facilitating a seamless workflow.
 
 ## Conclusion
-The integration of advanced attributes and functionalities into the CrewAI framework significantly enriches the agent collaboration ecosystem. These enhancements not only simplify interactions but also offer unprecedented flexibility and control, paving the way for sophisticated AI-driven solutions capable of tackling complex tasks through intelligent collaboration and delegation.
+The integration of advanced attributes and functionalities into the CrewAI framework significantly enriches the agent collaboration ecosystem. These enhancements not only simplify interactions but also offer unprecedented flexibility and control, paving the way for sophisticated AI-driven solutions capable of tackling complex tasks through intelligent collaboration and delegation.
\ No newline at end of file
diff --git a/docs/core-concepts/Crews.md b/docs/core-concepts/Crews.md
index 98e5f09c6..dddc4b18e 100644
--- a/docs/core-concepts/Crews.md
+++ b/docs/core-concepts/Crews.md
@@ -1,3 +1,4 @@
+```markdown
 ---
 title: crewAI Crews
 description: Understanding and utilizing crews in the crewAI framework.
@@ -9,20 +10,20 @@ description: Understanding and utilizing crews in the crewAI framework.
 
 ## Crew Attributes
 
-| Attribute            | Description                                                  |
-| :------------------- | :----------------------------------------------------------- |
-| **Tasks**            | A list of tasks assigned to the crew.                        |
-| **Agents**           | A list of agents that are part of the crew.                  |
-| **Process**          | The process flow (e.g., sequential, hierarchical) the crew follows. |
-| **Verbose**          | The verbosity level for logging during execution.            |
-| **Manager LLM**      | The language model used by the manager agent in a hierarchical process. **Required when using a hierarchical process.** |
-| **Function Calling LLM** | If passed crew will use this LLM to do function calling for tools for all agents in the crew |
-| **Config**           | Optional configuration settings for the crew, in `Json` or `Dict[str, Any]` format. |
-| **Max RPM**          | Maximum requests per minute the crew adheres to during execution. |
-| **Language**         | Language used for the crew, defaults to English.             |
-| **Full Output**      | Whether the crew should return the full output with all tasks outputs or just the final output. |
-| **Step Callback**    | A function that is called after each step of every agent. This can be used to log the agent's actions or to perform other operations; it won't override the agent-specific `step_callback`. |
-| **Share Crew**       | Whether you want to share the complete crew information and execution with the crewAI team to make the library better, and allow us to train models. |
+| Attribute               | Description                                                  |
+| :---------------------- | :----------------------------------------------------------- |
+| **Tasks**               | A list of tasks assigned to the crew.                        |
+| **Agents**              | A list of agents that are part of the crew.                  |
+| **Process** *(optional)*              | The process flow (e.g., sequential, hierarchical) the crew follows. |
+| **Verbose** *(optional)*              | The verbosity level for logging during execution.            |
+| **Manager LLM** *(optional)*          | The language model used by the manager agent in a hierarchical process. **Required when using a hierarchical process.** |
+| **Function Calling LLM** *(optional)* | If passed, the crew will use this LLM to do function calling for tools for all agents in the crew. Each agent can have its own LLM, which overrides the crew's LLM for function calling. |
+| **Config** *(optional)*               | Optional configuration settings for the crew, in `Json` or `Dict[str, Any]` format. |
+| **Max RPM** *(optional)*              | Maximum requests per minute the crew adheres to during execution. |
+| **Language**  *(optional)*            | Language used for the crew, defaults to English.             |
+| **Full Output** *(optional)*          | Whether the crew should return the full output with all tasks outputs or just the final output. |
+| **Step Callback** *(optional)*        | A function that is called after each step of every agent. This can be used to log the agent's actions or to perform other operations; it won't override the agent-specific `step_callback`. |
+| **Share Crew** *(optional)*           | Whether you want to share the complete crew information and execution with the crewAI team to make the library better, and allow us to train models. |
 
 !!! note "Crew Max RPM"
 		The `max_rpm` attribute sets the maximum number of requests per minute the crew can perform to avoid rate limits and will override individual agents' `max_rpm` settings if you set it.
@@ -47,12 +48,19 @@ researcher = Agent(
 
 writer = Agent(
     role='Content Writer',
-    goal='Write engaging articles on AI discoveries'
+    goal='Write engaging articles on AI discoveries',
+    verbose=True
 )
 
 # Create tasks for the agents
-research_task = Task(description='Identify breakthrough AI technologies', agent=researcher)
-write_article_task = Task(description='Draft an article on the latest AI technologies', agent=writer)
+research_task = Task(
+    description='Identify breakthrough AI technologies',
+    agent=researcher
+)
+write_article_task = Task(
+    description='Draft an article on the latest AI technologies',
+    agent=writer
+)
 
 # Assemble the crew with a sequential process
 my_crew = Crew(
@@ -60,14 +68,25 @@ my_crew = Crew(
     tasks=[research_task, write_article_task],
     process=Process.sequential,
     full_output=True,
-    verbose=True
+    verbose=True,
 )
 ```
 
+## Crew Usage Metrics
+
+After the crew execution, you can access the `usage_metrics` attribute to view the language model (LLM) usage metrics for all tasks executed by the crew. This provides insights into operational efficiency and areas for improvement.
+
+```python
+# Access the crew's usage metrics
+crew = Crew(agents=[agent1, agent2], tasks=[task1, task2])
+crew.kickoff()
+print(crew.usage_metrics)
+```
+
 ## Crew Execution Process
 
 - **Sequential Process**: Tasks are executed one after another, allowing for a linear flow of work.
-- **Hierarchical Process**: A manager agent coordinates the crew, delegating tasks and validating outcomes before proceeding. **Note**: A `manager_llm` is required for this process.
+- **Hierarchical Process**: A manager agent coordinates the crew, delegating tasks and validating outcomes before proceeding. **Note**: A `manager_llm` is required for this process and it's essential for validating the process flow.
 
 ### Kicking Off a Crew
 
@@ -77,4 +96,3 @@ Once your crew is assembled, initiate the workflow with the `kickoff()` method.
 # Start the crew's task execution
 result = my_crew.kickoff()
 print(result)
-```
\ No newline at end of file
diff --git a/docs/core-concepts/Processes.md b/docs/core-concepts/Processes.md
index 1c4479155..330b2dc82 100644
--- a/docs/core-concepts/Processes.md
+++ b/docs/core-concepts/Processes.md
@@ -10,26 +10,37 @@ description: Detailed guide on workflow management through processes in CrewAI,
 ## Process Implementations
 
 - **Sequential**: Executes tasks sequentially, ensuring tasks are completed in an orderly progression.
-- **Hierarchical**: Organizes tasks in a managerial hierarchy, where tasks are delegated and executed based on a structured chain of command, the manager for delegation is automatically created by crewAI.
-- **Consensual (Planned)**: A future process type aiming for collaborative decision-making among agents on task execution, introducing a more democratic approach to task management within CrewAI.
+- **Hierarchical**: Organizes tasks in a managerial hierarchy, where tasks are delegated and executed based on a structured chain of command. Note: A manager language model (`manager_llm`) must be specified in the crew to enable the hierarchical process, allowing for the creation and management of tasks by the manager.
+- **Consensual Process (Planned)**: Currently under consideration for future development, this process type aims for collaborative decision-making among agents on task execution, introducing a more democratic approach to task management within CrewAI. As of now, it is not implemented in the codebase.
 
 ## The Role of Processes in Teamwork
 Processes enable individual agents to operate as a cohesive unit, streamlining their efforts to achieve common objectives with efficiency and coherence.
 
 ## Assigning Processes to a Crew
-Specify the process type upon crew creation to set the execution strategy:
+To assign a process to a crew, specify the process type upon crew creation to set the execution strategy. Note: For a hierarchical process, ensure to define `manager_llm` for the manager agent.
 
 ```python
 from crewai import Crew
 from crewai.process import Process
+from langchain_openai import ChatOpenAI
 
 # Example: Creating a crew with a sequential process
-crew = Crew(agents=my_agents, tasks=my_tasks, process=Process.sequential)
+crew = Crew(
+    agents=my_agents,
+    tasks=my_tasks,
+    process=Process.sequential
+)
 
 # Example: Creating a crew with a hierarchical process
-crew = Crew(agents=my_agents, tasks=my_tasks, process=Process.hierarchical)
+# Ensure to provide a manager_llm
+crew = Crew(
+    agents=my_agents,
+    tasks=my_tasks,
+    process=Process.hierarchical,
+    manager_llm=ChatOpenAI(model="gpt-4")
+)
 ```
-**Note:** Ensure `my_agents` and `my_tasks` are defined prior to creating a `Crew` object.
+**Note:** Ensure `my_agents` and `my_tasks` are defined prior to creating a `Crew` object, and for the hierarchical process, `manager_llm` is also required.
 
 ## Sequential Process
 This method mirrors dynamic team workflows, progressing through tasks in a thoughtful and systematic manner. Task execution follows the predefined order in the task list, with the output of one task serving as context for the next.
@@ -37,13 +48,13 @@ This method mirrors dynamic team workflows, progressing through tasks in a thoug
 To customize task context, utilize the `context` parameter in the `Task` class to specify outputs that should be used as context for subsequent tasks.
 
 ## Hierarchical Process
-Emulates a corporate hierarchy. A "manager" agent is automatically created so it oversees task execution, including planning, delegation, and validation. Tasks are not pre-assigned; the manager allocates tasks to agents, reviews outputs, and assesses task completion.
+Emulates a corporate hierarchy, crewAI creates a manager automatically for you, requiring the specification of a manager language model (`manager_llm`) for the manager agent. This agent oversees task execution, including planning, delegation, and validation. Tasks are not pre-assigned; the manager allocates tasks to agents based on their capabilities, reviews outputs, and assesses task completion.
 
 ## Process Class: Detailed Overview
-The `Process` class is implemented as an enumeration (`Enum`), ensuring type safety and restricting process values to the defined types (`sequential` and `hierarchical`). This design choice guarantees that only valid processes are utilized within the CrewAI framework.
+The `Process` class is implemented as an enumeration (`Enum`), ensuring type safety and restricting process values to the defined types (`sequential`, `hierarchical`, and future `consensual`). This design choice guarantees that only valid processes are utilized within the CrewAI framework.
 
 ## Planned Future Processes
-- **Consensual Process**: A collaborative decision-making process among agents on task execution is planned but not currently implemented. This future enhancement will introduce a more democratic approach to task management within CrewAI.
+- **Consensual Process**: This collaborative decision-making process among agents on task execution is under consideration but not currently implemented. This future enhancement aims to introduce a more democratic approach to task management within CrewAI.
 
 ## Conclusion
-The structured collaboration facilitated by processes within CrewAI is crucial for enabling systematic teamwork among agents. Documentation will be updated to reflect new processes and enhancements, ensuring users have access to the most current and comprehensive information.
+The structured collaboration facilitated by processes within CrewAI is crucial for enabling systematic teamwork among agents. Documentation will be regularly updated to reflect new processes and enhancements, ensuring users have access to the most current and comprehensive information.
\ No newline at end of file
diff --git a/docs/core-concepts/Tasks.md b/docs/core-concepts/Tasks.md
index cb599d890..d10e872d8 100644
--- a/docs/core-concepts/Tasks.md
+++ b/docs/core-concepts/Tasks.md
@@ -1,3 +1,4 @@
+```markdown
 ---
 title: crewAI Tasks
 description: Overview and management of tasks within the crewAI framework.
@@ -17,10 +18,10 @@ Tasks in CrewAI can be designed to require collaboration between agents. For exa
 | **Agent**    | Optionally, you can specify which agent is responsible for the task. If not, the crew's process will determine who takes it on. |
 | **Expected Output**      | Clear and detailed definition of expected output for the task.  |
 | **Tools** *(optional)*   | These are the functions or capabilities the agent can utilize to perform the task. They can be anything from simple actions like 'search' to more complex interactions with other agents or APIs. |
-| **Async Execution** *(optional)*      | If the task should be executed asynchronously. This indicates that the crew will not wait for the task to be completed to continue with the next task. |
+| **Async Execution** *(optional)*      | Indicates whether the task should be executed asynchronously, allowing the crew to continue with the next task without waiting for completion. |
 | **Context**  *(optional)*     | Other tasks that will have their output used as context for this task. If a task is asynchronous, the system will wait for that to finish before using its output as context. |
-| **Output JSON**  *(optional)*     | Takes a pydantic model and returns the output as a JSON object. **Agent LLM needs to be using OpenAI client, could be Ollama for example but using the OpenAI wrapper** |
-| **Output Pydantic**  *(optional)*     | Takes a pydantic model and returns the output as a pydantic object. **Agent LLM needs to be using OpenAI client, could be Ollama for example but using the OpenAI wrapper** |
+| **Output JSON**  *(optional)*     | Takes a pydantic model and returns the output as a JSON object. **Agent LLM needs to be using an OpenAI client, could be Ollama for example but using the OpenAI wrapper** |
+| **Output Pydantic**  *(optional)*     | Takes a pydantic model and returns the output as a pydantic object. **Agent LLM needs to be using an OpenAI client, could be Ollama for example but using the OpenAI wrapper** |
 | **Output File**  *(optional)*     | Takes a file path and saves the output of the task on it. |
 | **Callback**  *(optional)*  | A function to be executed after the task is completed. |
 
@@ -48,10 +49,10 @@ Tools from the [crewAI Toolkit](https://github.com/joaomdmoura/crewai-tools) and
 ```python
 import os
 os.environ["OPENAI_API_KEY"] = "Your Key"
+os.environ["SERPER_API_KEY"] = "Your Key" # serper.dev API key
 
 from crewai import Agent, Task, Crew
-from langchain.agents import Tool
-from langchain_community.tools import DuckDuckGoSearchRun
+from crewai_tools import SerperDevTool
 
 research_agent = Agent(
     role='Researcher',
@@ -62,9 +63,7 @@ research_agent = Agent(
     verbose=True
 )
 
-# Install duckduckgo-search for this example:
-# !pip install -U duckduckgo-search
-search_tool = DuckDuckGoSearchRun()
+search_tool = SerperDevTool()
 
 task = Task(
   description='Find and summarize the latest AI news',
@@ -87,16 +86,25 @@ This demonstrates how tasks with specific tools can override an agent's default
 
 ## Referring to Other Tasks
 
-In crewAI, the output of one task is automatically relayed into the next one, but you can specifically define what tasks' output should be used as context for another task.
+In crewAI, the output of one task is automatically relayed into the next one, but you can specifically define what tasks' output, including multiple should be used as context for another task.
 
 This is useful when you have a task that depends on the output of another task that is not performed immediately after it. This is done through the `context` attribute of the task:
 
 ```python
 # ...
 
-research_task = Task(
+research_ai_task = Task(
   description='Find and summarize the latest AI news',
   expected_output='A bullet list summary of the top 5 most important AI news',
+  async_execution=True,
+  agent=research_agent,
+  tools=[search_tool]
+)
+
+research_ops_task = Task(
+  description='Find and summarize the latest AI Ops news',
+  expected_output='A bullet list summary of the top 5 most important AI Ops news',
+  async_execution=True,
   agent=research_agent,
   tools=[search_tool]
 )
@@ -105,7 +113,7 @@ write_blog_task = Task(
   description="Write a full blog post about the importance of AI and its latest news",
   expected_output='Full blog post that is 4 paragraphs long',
   agent=writer_agent,
-  context=[research_task]
+  context=[research_ai_task, research_ops_task]
 )
 
 #...
@@ -146,7 +154,7 @@ write_article = Task(
 
 ## Callback Mechanism
 
-You can define a callback function that will be executed after the task is completed. This is useful for tasks that need to trigger some side effect after they are completed, while the crew is still running.
+The callback function is executed after the task is completed, allowing for actions or notifications to be triggered based on the task's outcome.
 
 ```python
 # ...
@@ -217,5 +225,4 @@ These validations help in maintaining the consistency and reliability of task ex
 
 ## Conclusion
 
-Tasks are the driving force behind the actions of agents in crewAI. By properly defining tasks and their outcomes, you set the stage for your AI agents to work effectively, either independently or as a collaborative unit.
-Equipping tasks with appropriate tools and following robust validation practices is crucial for maximizing CrewAI's potential, ensuring agents are effectively prepared for their assignments and that tasks are executed as intended.
\ No newline at end of file
+Tasks are the driving force behind the actions of agents in crewAI. By properly defining tasks and their outcomes, you set the stage for your AI agents to work effectively, either independently or as a collaborative unit. Equipping tasks with appropriate tools, understanding the execution process, and following robust validation practices are crucial for maximizing CrewAI's potential, ensuring agents are effectively prepared for their assignments and that tasks are executed as intended.
\ No newline at end of file
diff --git a/docs/core-concepts/Tools.md b/docs/core-concepts/Tools.md
index 8b7e8f2f1..c9147cc6c 100644
--- a/docs/core-concepts/Tools.md
+++ b/docs/core-concepts/Tools.md
@@ -1,3 +1,4 @@
+```
 ---
 title: crewAI Tools
 description: Understanding and leveraging tools within the crewAI framework for agent collaboration and task execution.
@@ -12,41 +13,40 @@ CrewAI tools empower agents with capabilities ranging from web searching and dat
 
 ## Key Characteristics of Tools
 
-- **Utility**: Designed for various tasks such as web searching, data analysis, content generation, and agent collaboration.
-- **Integration**: Enhances agent capabilities by integrating tools directly into their workflow.
-- **Customizability**: Offers flexibility to develop custom tools or use existing ones, catering to specific agent needs.
+- **Utility**: Crafted for tasks such as web searching, data analysis, content generation, and agent collaboration.
+- **Integration**: Boosts agent capabilities by seamlessly integrating tools into their workflow.
+- **Customizability**: Provides the flexibility to develop custom tools or utilize existing ones, catering to the specific needs of agents.
 
 ## Using crewAI Tools
 
-crewAI comes with a series to built-in tools that can be used to extend the capabilities of your agents. Start by installing our extra tools package:
+To enhance your agents' capabilities with crewAI tools, begin by installing our extra tools package:
 
 ```bash
 pip install 'crewai[tools]'
 ```
 
-Here is an example on how to use them:
+Here's an example demonstrating their use:
 
 ```python
 import os
 from crewai import Agent, Task, Crew
-# Importing some of the crewAI tools
+# Importing crewAI tools
 from crewai_tools import (
     DirectoryReadTool,
     FileReadTool,
-    SeperDevTool,
+    SerperDevTool,
     WebsiteSearchTool
 )
 
-# get a free account in serper.dev
+# Set up API keys
 os.environ["SERPER_API_KEY"] = "Your Key"
 os.environ["OPENAI_API_KEY"] = "Your Key"
 
 # Instantiate tools
-# Assumes this ./blog-posts exists with existing blog posts on it
-docs_tools = DirectoryReadTool(directory='./blog-posts')
-file_read_tool = FileReadTool()
+docs_tool = DirectoryReadTool(directory='./blog-posts')
+file_tool = FileReadTool()
 search_tool = SeperDevTool()
-website_rag = WebsiteSearchTool()
+web_rag_tool = WebsiteSearchTool()
 
 # Create agents
 researcher = Agent(
@@ -59,35 +59,34 @@ researcher = Agent(
 
 writer = Agent(
     role='Content Writer',
-    goal='Write amazing, super engaging blog post about the AI industry',
+    goal='Craft engaging blog posts about the AI industry',
     backstory='A skilled writer with a passion for technology.',
-    tools=[docs_tools, file_read_tool],
+    tools=[docs_tool, file_tool],
     verbose=True
 )
 
-# Create  tasks
+# Define tasks
 research = Task(
-    description='Research the AI industry and provide a summary of the latest most trending matters and developments.',
-    expected_output='A summary of the top 3 latest most trending matters and developments in the AI industry with you unique take on why they matter.',
+    description='Research the latest trends in the AI industry and provide a summary.',
+    expected_output='A summary of the top 3 trending developments in the AI industry with a unique perspective on their significance.',
     agent=researcher
 )
 
 write = Task(
-    description='Write an engaging blog post about the AI industry, using the summary provided by the research analyst. Read the latest blog posts in the directory to get inspiration.',
-    expected_output='A 4 paragraph blog post formatted as markdown with proper subtitles about the latest trends that is engaging and informative and funny, avoid complex words and make it easy to read.',
+    description='Write an engaging blog post about the AI industry, based on the research analyst’s summary. Draw inspiration from the latest blog posts in the directory.',
+    expected_output='A 4-paragraph blog post formatted in markdown with engaging, informative, and accessible content, avoiding complex jargon.',
     agent=writer,
-    output_file='blog-posts/new_post.md' # The final blog post will be written here
+    output_file='blog-posts/new_post.md'  # The final blog post will be saved here
 )
 
-
-# Create a crew
+# Assemble a crew
 crew = Crew(
     agents=[researcher, writer],
     tasks=[research, write],
     verbose=2
 )
 
-# Execute the tasks
+# Execute tasks
 crew.kickoff()
 ```
 
@@ -156,7 +155,7 @@ class MyCustomTool(BaseTool):
 
     def _run(self, argument: str) -> str:
         # Implementation goes here
-        pass
+        return "Result from custom tool"
 ```
 
 Define a new class inheriting from `BaseTool`, specifying `name`, `description`, and the `_run` method for operational logic.
@@ -230,4 +229,4 @@ agent = Agent(
 ```
 
 ## Conclusion
-Tools are crucial for extending the capabilities of CrewAI agents, allowing them to undertake a diverse array of tasks and collaborate efficiently. When building your AI solutions with CrewAI, consider both custom and existing tools to empower your agents and foster a dynamic AI ecosystem.
+Tools are pivotal in extending the capabilities of CrewAI agents, enabling them to undertake a broad spectrum of tasks and collaborate effectively. When building solutions with CrewAI, leverage both custom and existing tools to empower your agents and enhance the AI ecosystem.
\ No newline at end of file
diff --git a/docs/how-to/Create-Custom-Tools.md b/docs/how-to/Create-Custom-Tools.md
new file mode 100644
index 000000000..d9f477a0a
--- /dev/null
+++ b/docs/how-to/Create-Custom-Tools.md
@@ -0,0 +1,68 @@
+---
+title: Creating your own Tools
+description: Guide on how to create and use custom tools within the crewAI framework.
+---
+
+## Creating your own Tools
+!!! example "Custom Tool Creation"
+    Developers can craft custom tools tailored for their agent’s needs or utilize pre-built options:
+
+To create your own crewAI tools you will need to install our extra tools package:
+
+```bash
+pip install 'crewai[tools]'
+```
+
+Once you do that there are two main ways for one to create a crewAI tool:
+
+### Subclassing `BaseTool`
+
+```python
+from crewai_tools import BaseTool
+
+class MyCustomTool(BaseTool):
+    name: str = "Name of my tool"
+    description: str = "Clear description for what this tool is useful for, you agent will need this information to use it."
+
+    def _run(self, argument: str) -> str:
+        # Implementation goes here
+        return "Result from custom tool"
+```
+
+Define a new class inheriting from `BaseTool`, specifying `name`, `description`, and the `_run` method for operational logic.
+
+
+### Utilizing the `tool` Decorator
+
+For a simpler approach, create a `Tool` object directly with the required attributes and a functional logic.
+
+```python
+from crewai_tools import tool
+@tool("Name of my tool")
+def my_tool(question: str) -> str:
+    """Clear description for what this tool is useful for, you agent will need this information to use it."""
+    # Function logic here
+```
+
+```python
+import json
+import requests
+from crewai import Agent
+from crewai.tools import tool
+from unstructured.partition.html import partition_html
+
+    # Annotate the function with the tool decorator from crewAI
+@tool("Integration with a given API")
+def integtation_tool(argument: str) -> str:
+    """Integration with a given API"""
+    # Code here
+    return resutls # string to be sent back to the agent
+
+# Assign the scraping tool to an agent
+agent = Agent(
+    role='Research Analyst',
+    goal='Provide up-to-date market analysis',
+    backstory='An expert analyst with a keen eye for market trends.',
+    tools=[integtation_tool]
+)
+```
\ No newline at end of file
diff --git a/docs/how-to/Creating-a-Crew-and-kick-it-off.md b/docs/how-to/Creating-a-Crew-and-kick-it-off.md
index 6a7033f7d..fd72d1a7f 100644
--- a/docs/how-to/Creating-a-Crew-and-kick-it-off.md
+++ b/docs/how-to/Creating-a-Crew-and-kick-it-off.md
@@ -7,12 +7,11 @@ description: A comprehensive guide to creating a dynamic CrewAI team for your pr
 Embark on your CrewAI journey by setting up your environment and initiating your AI crew with enhanced features. This guide ensures a seamless start, incorporating the latest updates.
 
 ## Step 0: Installation
-Install CrewAI and any necessary packages for your project. The `duckduckgo-search` package is highlighted here for enhanced search capabilities.
+Install CrewAI and any necessary packages for your project.
 
 ```shell
 pip install crewai
-pip install crewai[tools]
-pip install duckduckgo-search
+pip install 'crewai[tools]'
 ```
 
 ## Step 1: Assemble Your Agents
@@ -20,24 +19,24 @@ Define your agents with distinct roles, backstories, and now, enhanced capabilit
 
 ```python
 import os
+os.environ["SERPER_API_KEY"] = "Your Key" # serper.dev API key
 os.environ["OPENAI_API_KEY"] = "Your Key"
 
 from crewai import Agent
-from langchain_community.tools import DuckDuckGoSearchRun
-search_tool = DuckDuckGoSearchRun()
-
-# Topic for the crew run
-topic = 'AI in healthcare'
+from crewai_tools import SerperDevTool
+search_tool = SerperDevTool()
 
 # Creating a senior researcher agent with memory and verbose mode
 researcher = Agent(
   role='Senior Researcher',
-  goal=f'Uncover groundbreaking technologies in {topic}',
+  goal='Uncover groundbreaking technologies in {topic}',
   verbose=True,
   memory=True,
-  backstory="""Driven by curiosity, you're at the forefront of
-  innovation, eager to explore and share knowledge that could change
-  the world.""",
+  backstory=(
+    "Driven by curiosity, you're at the forefront of"
+    "innovation, eager to explore and share knowledge that could change"
+    "the world."
+  ),
   tools=[search_tool],
   allow_delegation=True
 )
@@ -45,12 +44,14 @@ researcher = Agent(
 # Creating a writer agent with custom tools and delegation capability
 writer = Agent(
   role='Writer',
-  goal=f'Narrate compelling tech stories about {topic}',
+  goal='Narrate compelling tech stories about {topic}',
   verbose=True,
   memory=True,
-  backstory="""With a flair for simplifying complex topics, you craft
-  engaging narratives that captivate and educate, bringing new
-  discoveries to light in an accessible manner.""",
+  backstory=(
+    "With a flair for simplifying complex topics, you craft"
+    "engaging narratives that captivate and educate, bringing new"
+    "discoveries to light in an accessible manner."
+  ),
   tools=[search_tool],
   allow_delegation=False
 )
@@ -64,10 +65,12 @@ from crewai import Task
 
 # Research task
 research_task = Task(
-  description=f"""Identify the next big trend in {topic}.
-  Focus on identifying pros and cons and the overall narrative.
-  Your final report should clearly articulate the key points,
-  its market opportunities, and potential risks.""",
+  description=(
+    "Identify the next big trend in {topic}."
+    "Focus on identifying pros and cons and the overall narrative."
+    "Your final report should clearly articulate the key points"
+    "its market opportunities, and potential risks."
+  ),
   expected_output='A comprehensive 3 paragraphs long report on the latest AI trends.',
   tools=[search_tool],
   agent=researcher,
@@ -75,10 +78,12 @@ research_task = Task(
 
 # Writing task with language model configuration
 write_task = Task(
-  description=f"""Compose an insightful article on {topic}.
-  Focus on the latest trends and how it's impacting the industry.
-  This article should be easy to understand, engaging, and positive.""",
-  expected_output=f'A 4 paragraph article on {topic} advancements fromated as markdown.',
+  description=(
+    "Compose an insightful article on {topic}."
+    "Focus on the latest trends and how it's impacting the industry."
+    "This article should be easy to understand, engaging, and positive."
+  ),
+  expected_output='A 4 paragraph article on {topic} advancements formatted as markdown.',
   tools=[search_tool],
   agent=writer,
   async_execution=False,
@@ -101,11 +106,11 @@ crew = Crew(
 ```
 
 ## Step 4: Kick It Off
-Initiate the process with your enhanced crew ready. Observe as your agents collaborate, leveraging their new capabilities for a successful project outcome.
+Initiate the process with your enhanced crew ready. Observe as your agents collaborate, leveraging their new capabilities for a successful project outcome. You can also pass the inputs that will be interpolated into the agents and tasks.
 
 ```python
 # Starting the task execution process with enhanced feedback
-result = crew.kickoff()
+result = crew.kickoff(inputs={'topic': 'AI in healthcare'})
 print(result)
 ```
 
diff --git a/docs/how-to/Customizing-Agents.md b/docs/how-to/Customizing-Agents.md
index 71fa4ff61..3028ae608 100644
--- a/docs/how-to/Customizing-Agents.md
+++ b/docs/how-to/Customizing-Agents.md
@@ -17,6 +17,7 @@ Beyond the basic attributes, CrewAI allows for deeper customization to enhance a
 
 ### Language Model Customization
 Agents can be customized with specific language models (`llm`) and function-calling language models (`function_calling_llm`), offering advanced control over their processing and decision-making abilities.
+By default crewAI agents are ReAct agents, but by setting the `function_calling_llm` you can turn them into a function calling agents.
 
 ### Enabling Memory for Agents
 CrewAI supports memory for agents, enabling them to remember past interactions. This feature is critical for tasks requiring awareness of previous contexts or decisions.
@@ -25,11 +26,11 @@ CrewAI supports memory for agents, enabling them to remember past interactions.
 Adjusting an agent's performance and monitoring its operations are crucial for efficient task execution.
 
 ### Verbose Mode and RPM Limit
-- **Verbose Mode**: Enables detailed logging of an agent's actions, useful for debugging and optimization.
+- **Verbose Mode**: Enables detailed logging of an agent's actions, useful for debugging and optimization. Specifically, it provides insights into agent execution processes, aiding in the optimization of performance.
 - **RPM Limit**: Sets the maximum number of requests per minute (`max_rpm`), controlling the agent's query frequency to external services.
 
 ### Maximum Iterations for Task Execution
-The `max_iter` attribute allows users to define the maximum number of iterations an agent can perform for a single task, preventing infinite loops or excessively long executions.
+The `max_iter` attribute allows users to define the maximum number of iterations an agent can perform for a single task, preventing infinite loops or excessively long executions. The default value is set to 15, providing a balance between thoroughness and efficiency. Once the agent approaches this number it will try it's best to give a good answer.
 
 ## Customizing Agents and Tools
 Agents are customized by defining their attributes and tools during initialization. Tools are critical for an agent's functionality, enabling them to perform specialized tasks. In this example we will use the crewAI tools package to create a tool for a research analyst agent.
@@ -42,31 +43,31 @@ pip install 'crewai[tools]'
 ```python
 import os
 from crewai import Agent
-from crewai_tools import SeperDevTool
+from crewai_tools import SerperDevTool
 
 # Set API keys for tool initialization
 os.environ["OPENAI_API_KEY"] = "Your Key"
 os.environ["SERPER_API_KEY"] = "Your Key"
 
 # Initialize a search tool
-search_tool = SeperDevTool()
+search_tool = SerperDevTool()
 
 # Initialize the agent with advanced options
 agent = Agent(
   role='Research Analyst',
   goal='Provide up-to-date market analysis',
   backstory='An expert analyst with a keen eye for market trends.',
-  tools=[serper_tool],
+  tools=[search_tool],
   memory=True,
   verbose=True,
-  max_rpm=10, # Optinal: Limit requests to 10 per minute, preventing API abuse
-  max_iter=5, # Optional: Limit task iterations to 5 before the agent tried to gives its best answer
+  max_rpm=10, # Optional: Limit requests to 10 per minute, preventing API abuse
+  max_iter=5, # Optional: Limit task iterations to 5 before the agent tries to give its best answer
   allow_delegation=False
 )
 ```
 
 ## Delegation and Autonomy
-Controlling an agent's ability to delegate tasks or ask questions is vital for tailoring its autonomy and collaborative dynamics within the CrewAI framework.
+Controlling an agent's ability to delegate tasks or ask questions is vital for tailoring its autonomy and collaborative dynamics within the crewAI framework. By default, the `allow_delegation` attribute is set to `True`, enabling agents to seek assistance or delegate tasks as needed. This default behavior promotes collaborative problem-solving and efficiency within the crewAI ecosystem.
 
 ### Example: Disabling Delegation for an Agent
 ```python
@@ -79,4 +80,4 @@ agent = Agent(
 ```
 
 ## Conclusion
-Customizing agents in CrewAI by setting their roles, goals, backstories, and tools, alongside advanced options like language model customization, memory, and performance settings, equips a nuanced and capable AI team ready for complex challenges.
\ No newline at end of file
+Customizing agents in CrewAI by setting their roles, goals, backstories, and tools, alongside advanced options like language model customization, memory, performance settings, and delegation preferences, equips a nuanced and capable AI team ready for complex challenges.
\ No newline at end of file
diff --git a/docs/how-to/Hierarchical.md b/docs/how-to/Hierarchical.md
index 5ed5f1656..c92579d5e 100644
--- a/docs/how-to/Hierarchical.md
+++ b/docs/how-to/Hierarchical.md
@@ -1,60 +1,61 @@
 ---
 title: Implementing the Hierarchical Process in CrewAI
-description: Understanding and applying the hierarchical process within your CrewAI projects, with updates reflecting the latest coding practices.
+description: A comprehensive guide to understanding and applying the hierarchical process within your CrewAI projects, updated to reflect the latest coding practices and functionalities.
 ---
 
 ## Introduction
-The hierarchical process in CrewAI introduces a structured approach to managing tasks, mimicking traditional organizational hierarchies for efficient task delegation and execution. This ensures a systematic workflow that enhances project outcomes.
+The hierarchical process in CrewAI introduces a structured approach to task management, simulating traditional organizational hierarchies for efficient task delegation and execution. This systematic workflow enhances project outcomes by ensuring tasks are handled with optimal efficiency and accuracy.
 
 !!! note "Complexity and Efficiency"
     The hierarchical process is designed to leverage advanced models like GPT-4, optimizing token usage while handling complex tasks with greater efficiency.
 
 ## Hierarchical Process Overview
-Tasks within this process are managed through a clear hierarchy, where a 'manager' agent coordinates the workflow, delegates tasks, and validates outcomes, ensuring a streamlined and effective execution process.
+By default, tasks in CrewAI are managed through a sequential process. However, adopting a hierarchical approach allows for a clear hierarchy in task management, where a 'manager' agent coordinates the workflow, delegates tasks, and validates outcomes for streamlined and effective execution. This manager agent is automatically created by crewAI so you don't need to worry about it.
 
 ### Key Features
-- **Task Delegation**: A manager agent is responsible for allocating tasks among crew members based on their roles and capabilities.
-- **Result Validation**: The manager evaluates the outcomes to ensure they meet the required standards before moving forward.
-- **Efficient Workflow**: Emulates corporate structures, offering an organized and familiar approach to task management.
+- **Task Delegation**: A manager agent allocates tasks among crew members based on their roles and capabilities.
+- **Result Validation**: The manager evaluates outcomes to ensure they meet the required standards.
+- **Efficient Workflow**: Emulates corporate structures, providing an organized approach to task management.
 
 ## Implementing the Hierarchical Process
-To adopt the hierarchical process, define a crew with a designated manager and establish a clear chain of command for task execution. This structure is crucial for maintaining an orderly and efficient workflow.
+To utilize the hierarchical process, it's essential to explicitly set the process attribute to `Process.hierarchical`, as the default behavior is `Process.sequential`. Define a crew with a designated manager and establish a clear chain of command.
 
 !!! note "Tools and Agent Assignment"
-    Tools should be assigned at the agent level, not the task level, to facilitate task delegation and execution by the designated agents under the manager's guidance.
+    Assign tools at the agent level to facilitate task delegation and execution by the designated agents under the manager's guidance.
 
-!!! note "Manager LLM Configuration"
-    A manager LLM is automatically assigned to the crew, eliminating the need for manual definition. However, configuring the `manager_llm` parameter is necessary to tailor the manager's decision-making process.
+!!! note "Manager LLM Requirement"
+    Configuring the `manager_llm` parameter is crucial for the hierarchical process. The system requires a manager LLM to be set up for proper function, ensuring tailored decision-making.
 
 ```python
 from langchain_openai import ChatOpenAI
 from crewai import Crew, Process, Agent
 
-# Agents are defined without specifying a manager explicitly
+# Agents are defined with an optional tools parameter
 researcher = Agent(
-	role='Researcher',
-	goal='Conduct in-depth analysis',
-	# tools = [...]
+    role='Researcher',
+    goal='Conduct in-depth analysis',
+    # tools=[]  # This can be optionally specified; defaults to an empty list
 )
 writer = Agent(
-	role='Writer',
-	goal='Create engaging content',
-	# tools = [...]
+    role='Writer',
+    goal='Create engaging content',
+    # tools=[]  # Optionally specify tools; defaults to an empty list
 )
 
 # Establishing the crew with a hierarchical process
 project_crew = Crew(
-	tasks=[...],  # Tasks to be delegated and executed under the manager's supervision
-	agents=[researcher, writer],
-	manager_llm=ChatOpenAI(temperature=0, model="gpt-4"),  # Defines the manager's decision-making engine
-	process=Process.hierarchical  # Specifies the hierarchical management approach
+    tasks=[...],  # Tasks to be delegated and executed under the manager's supervision
+    agents=[researcher, writer],
+    manager_llm=ChatOpenAI(temperature=0, model="gpt-4"),  # Mandatory for hierarchical process
+    process=Process.hierarchical  # Specifies the hierarchical management approach
 )
 ```
 
 ### Workflow in Action
-1. **Task Assignment**: The manager strategically assigns tasks, considering each agent's role and skills.
-2. **Execution and Review**: Agents complete their tasks, followed by a thorough review by the manager to ensure quality standards.
-3. **Sequential Task Progression**: The manager ensures tasks are completed in a logical order, facilitating smooth project progression.
+1. **Task Assignment**: The manager assigns tasks strategically, considering each agent's capabilities.
+2. **Execution and Review**: Agents complete their tasks, with the manager ensuring quality standards.
+3. **Sequential Task Progression**: Despite being a hierarchical process, tasks follow a logical order for smooth progression, facilitated by the manager's oversight.
+
 
 ## Conclusion
-Adopting the hierarchical process in CrewAI facilitates a well-organized and efficient approach to project management. By structuring tasks and delegations within a clear hierarchy, it enhances both productivity and quality control, making it an ideal strategy for managing complex projects.
\ No newline at end of file
+Adopting the hierarchical process in crewAI, with the correct configurations and understanding of the system's capabilities, facilitates an organized and efficient approach to project management.
\ No newline at end of file
diff --git a/docs/how-to/Human-Input-on-Execution.md b/docs/how-to/Human-Input-on-Execution.md
index 06c2d0054..02e9df429 100644
--- a/docs/how-to/Human-Input-on-Execution.md
+++ b/docs/how-to/Human-Input-on-Execution.md
@@ -1,6 +1,7 @@
+```markdown
 # Human Input in Agent Execution
 
-Human input is crucial in numerous agent execution scenarios, enabling agents to request additional information or clarification when necessary. This feature is particularly useful in complex decision-making processes or when agents require further details to complete a task effectively.
+Human input plays a pivotal role in several agent execution scenarios, enabling agents to seek additional information or clarification when necessary. This capability is invaluable in complex decision-making processes or when agents need more details to complete a task effectively.
 
 ## Using Human Input with CrewAI
 
@@ -8,25 +9,35 @@ Incorporating human input with CrewAI is straightforward, enhancing the agent's
 
 ### Example:
 
+```shell
+pip install crewai
+pip install 'crewai[tools]'
+```
+
 ```python
 import os
-from crewai import Agent, Task, Crew, Process
-from langchain_community.tools import DuckDuckGoSearchRun
+from crewai import Agent, Task, Crew
+from crewai_tools import SerperDevTool
+
 from langchain.agents import load_tools
 
-search_tool = DuckDuckGoSearchRun()
+os.environ["SERPER_API_KEY"] = "Your Key" # serper.dev API key
+os.environ["OPENAI_API_KEY"] = "Your Key"
+
 
 # Loading Human Tools
 human_tools = load_tools(["human"])
+search_tool = SerperDevTool()
 
-# Define your agents with roles and goals
+# Define your agents with roles, goals, and tools
 researcher = Agent(
   role='Senior Research Analyst',
   goal='Uncover cutting-edge developments in AI and data science',
-  backstory="""You are a Senior Research Analyst at a leading tech think tank.
-  Your expertise lies in identifying emerging trends and technologies in AI and
-  data science. You have a knack for dissecting complex data and presenting
-  actionable insights.""",
+  backstory=(
+    "You are a Senior Research Analyst at a leading tech think tank."
+    "Your expertise lies in identifying emerging trends and technologies in AI and data science."
+    "You have a knack for dissecting complex data and presenting actionable insights."
+  ),
   verbose=True,
   allow_delegation=False,
   tools=[search_tool]+human_tools # Passing human tools to the agent
@@ -34,31 +45,33 @@ researcher = Agent(
 writer = Agent(
   role='Tech Content Strategist',
   goal='Craft compelling content on tech advancements',
-  backstory="""You are a renowned Tech Content Strategist, known for your insightful
-  and engaging articles on technology and innovation. With a deep understanding of
-  the tech industry, you transform complex concepts into compelling narratives.""",
+  backstory=(
+    "You are a renowned Tech Content Strategist, known for your insightful and engaging articles on technology and innovation."
+    "With a deep understanding of the tech industry, you transform complex concepts into compelling narratives."
+  ),
   verbose=True,
   allow_delegation=True
 )
 
 # Create tasks for your agents
 task1 = Task(
-  description="""Conduct a comprehensive analysis of the latest advancements in AI in 2024.
-  Identify key trends, breakthrough technologies, and potential industry impacts.
-  Compile your findings in a detailed report.
-  Make sure to check with a human if the draft is good before finalizing your answer.""",
+  description=(
+    "Conduct a comprehensive analysis of the latest advancements in AI in 2024."
+    "Identify key trends, breakthrough technologies, and potential industry impacts."
+    "Compile your findings in a detailed report."
+    "Make sure to check with a human if the draft is good before finalizing your answer."
+  ),
   expected_output='A comprehensive full report on the latest AI advancements in 2024, leave nothing out',
-  agent=researcher
+  agent=researcher,
 )
 
 task2 = Task(
-  description="""Using the insights from the researcher's report, develop an engaging blog
-  post that highlights the most significant AI advancements.
-  Your post should be informative yet accessible, catering to a tech-savvy audience.
-  Aim for a narrative that captures the essence of these breakthroughs and their
-  implications for the future.
-  Your final answer MUST be the full blog post of at least 3 paragraphs.""",
-  expected_output='A compelling 3 paragraphs blog post formated as markdown about the latest AI advancements in 2024',
+  description=(
+    "Using the insights from the researcher's report, develop an engaging blog post that highlights the most significant AI advancements."
+    "Your post should be informative yet accessible, catering to a tech-savvy audience."
+    "Aim for a narrative that captures the essence of these breakthroughs and their implications for the future."
+  ),
+  expected_output='A compelling 3 paragraphs blog post formatted as markdown about the latest AI advancements in 2024',
   agent=writer
 )
 
diff --git a/docs/how-to/LLM-Connections.md b/docs/how-to/LLM-Connections.md
index d9f55a952..1693d6efa 100644
--- a/docs/how-to/LLM-Connections.md
+++ b/docs/how-to/LLM-Connections.md
@@ -1,6 +1,6 @@
 ---
 title: Connect CrewAI to LLMs
-description: Guide on integrating CrewAI with various Large Language Models (LLMs).
+description: Comprehensive guide on integrating CrewAI with various Large Language Models (LLMs), including detailed class attributes and methods.
 ---
 
 ## Connect CrewAI to LLMs
@@ -10,15 +10,22 @@ description: Guide on integrating CrewAI with various Large Language Models (LLM
 CrewAI offers flexibility in connecting to various LLMs, including local models via [Ollama](https://ollama.ai) and different APIs like Azure. It's compatible with all [LangChain LLM](https://python.langchain.com/docs/integrations/llms/) components, enabling diverse integrations for tailored AI solutions.
 
 ## CrewAI Agent Overview
-The `Agent` class in CrewAI is central to implementing AI solutions. Here's a brief overview:
+The `Agent` class is the cornerstone for implementing AI solutions in CrewAI. Here's an updated overview reflecting the latest codebase changes:
 
 - **Attributes**:
     - `role`: Defines the agent's role within the solution.
     - `goal`: Specifies the agent's objective.
     - `backstory`: Provides a background story to the agent.
     - `llm`: Indicates the Large Language Model the agent uses.
+    - `function_calling_llm` *Optinal*: Will turn the ReAct crewAI agent into a function calling agent.
+    - `max_iter`: Maximum number of iterations for an agent to execute a task, default is 15.
+    - `memory`: Enables the agent to retain information during the execution.
+    - `max_rpm`: Sets the maximum number of requests per minute.
+    - `verbose`: Enables detailed logging of the agent's execution.
+    - `allow_delegation`: Allows the agent to delegate tasks to other agents, default is `True`.
+    - `tools`: Specifies the tools available to the agent for task execution.
+    - `step_callback`: Provides a callback function to be executed after each step.
 
-### Example Changing OpenAI's GPT model
 ```python
 # Required
 os.environ["OPENAI_MODEL_NAME"]="gpt-4-0125-preview"
diff --git a/docs/index.md b/docs/index.md
index 1bd931e01..7228e8460 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -43,6 +43,11 @@ Cutting-edge framework for orchestrating role-playing, autonomous AI agents. By
                     Getting Started
                 </a>
             </li>
+            <li>
+                <a href="./how-to/Create Custom Tools">
+                    Create Custom Tools
+                </a>
+            </li>
             <li>
                 <a href="./how-to/Sequential">
                     Using Sequential Process
diff --git a/docs/telemetry/Telemetry.md b/docs/telemetry/Telemetry.md
index da2ad0eef..ca8d1e81d 100644
--- a/docs/telemetry/Telemetry.md
+++ b/docs/telemetry/Telemetry.md
@@ -1,23 +1,32 @@
+```markdown
 ## Telemetry
 
 CrewAI utilizes anonymous telemetry to gather usage statistics with the primary goal of enhancing the library. Our focus is on improving and developing the features, integrations, and tools most utilized by our users.
 
-It's pivotal to understand that **NO data is collected** concerning prompts, task descriptions, agents' backstories or goals, usage of tools, API calls, responses, any data processed by the agents, or secrets and environment variables.
+It's pivotal to understand that **NO data is collected** concerning prompts, task descriptions, agents' backstories or goals, usage of tools, API calls, responses, any data processed by the agents, or secrets and environment variables, with the exception of the conditions mentioned. When the `share_crew` feature is enabled, detailed data including task descriptions, agents' backstories or goals, and other specific attributes are collected to provide deeper insights while respecting user privacy.
 
 ### Data Collected Includes:
 - **Version of CrewAI**: Assessing the adoption rate of our latest version helps us understand user needs and guide our updates.
 - **Python Version**: Identifying the Python versions our users operate with assists in prioritizing our support efforts for these versions.
 - **General OS Information**: Details like the number of CPUs and the operating system type (macOS, Windows, Linux) enable us to focus our development on the most used operating systems and explore the potential for OS-specific features.
+- **Platform-Specific Information**: Collection of `platform`, `platform_release`, `platform_system`, and `platform_version` provides a comprehensive overview of the users' operating systems.
 - **Number of Agents and Tasks in a Crew**: Ensures our internal testing mirrors real-world scenarios, helping us guide users towards best practices.
-- **Crew Process Utilization**: Understanding how crews are utilized aids in directing our development focus.
+- **Crew Process Utilization**: Understanding how crews are utilized aids in directing our development focus. Attributes such as `crew_process` including execution details are collected for this purpose.
 - **Memory and Delegation Use by Agents**: Insights into how these features are used help evaluate their effectiveness and future.
 - **Task Execution Mode**: Knowing whether tasks are executed in parallel or sequentially influences our emphasis on enhancing parallel execution capabilities.
-- **Language Model Utilization**: Supports our goal to improve support for the most popular languages among our users.
+- **Language Model Utilization**: Supports our goal to improve support for the most popular languages among our users. This includes the collection of `crew_language` to indicate the default language model being used.
 - **Roles of Agents within a Crew**: Understanding the various roles agents play aids in crafting better tools, integrations, and examples.
-- **Tool Usage**: Identifying which tools are most frequently used allows us to prioritize improvements in those areas.
+- **Tool Usage**: Identifying which tools are most frequently used allows us to prioritize improvements in those areas. This includes the collection of tool names used by agents and tasks.
+- **Crew and Agent Specific Attributes**: Information such as `crew_id`, `verbose?`, `max_iter`, `max_rpm`, `i18n.language`, and `llm` attributes (like `name`, `model_name`, `base_url`, `model`, `top_k`, `temperature`) are collected to enhance our understanding and support of the ecosystem.
 
-### Opt-In Futher Telemetry Sharing
-Users can choose to share their complete telemetry data by enabling the `share_crew` attribute to `True` in their crew configurations. This opt-in approach respects user privacy and aligns with data protection standards by ensuring users have control over their data sharing preferences.
+### Opt-In Further Telemetry Sharing
+Users can choose to share their complete telemetry data by enabling the `share_crew` attribute to `True` in their crew configurations. This opt-in approach respects user privacy and aligns with data protection standards by ensuring users have control over their data sharing preferences. Enabling `share_crew` results in the collection of detailed `crew` and `task` execution data, including `goal`, `backstory`, `context`, and `output` of tasks. This enables a deeper insight into usage patterns while respecting the user's choice to share.
 
 ### Updates and Revisions
 We are committed to maintaining the accuracy and transparency of our documentation. Regular reviews and updates are performed to ensure our documentation accurately reflects the latest developments of our codebase and telemetry practices. Users are encouraged to review this section for the most current information on our data collection practices and how they contribute to the improvement of CrewAI.
+
+### Transparency and Review
+To foster greater transparency, users can inquire about the telemetry data being collected by contacting our support team. This initiative aims to provide users with the opportunity to understand the scope of our data collection practices better and aligns with our commitment to transparency and trust.
+
+By ensuring the documentation is up-to-date with these changes, we aim to maintain transparency with our users, fostering trust, and promoting an understanding of how telemetry data is used to enhance CrewAI.
+```
\ No newline at end of file
diff --git a/src/crewai/tools/tool_usage.py b/src/crewai/tools/tool_usage.py
index ee3fabbd3..010d20a4b 100644
--- a/src/crewai/tools/tool_usage.py
+++ b/src/crewai/tools/tool_usage.py
@@ -155,7 +155,6 @@ class ToolUsage:
                 self.task.increment_tools_errors()
                 return self.use(calling=calling, tool_string=tool_string)
 
-            print('LET"S GOOOOOOOO')
             self.tools_handler.on_tool_use(calling=calling, output=result)
 
         self._printer.print(content=f"\n\n{result}\n", color="yellow")