Your job is to generate the tools.jsonl file for the {domain} domain.
Specifically, you will be writing the tools specification for an automated chatbot agent that assists a customer based on the given policy.
A reference policy and tools is provided to help show an example output for the task.

Your task is as follows:
1. Read and think about the provided policy and list out the tools that are mentioned in the policy or should exist to support the agent's actions in the policy.
2. Deliberate about the input properties and the return types of the tools.
4. Devise a description and docstring for each tool, as it will be provided to the agent to to be used for interaction with a downstream system.
5. Create a functional json specification of the tools with correct formatting. Each tool must have the top level keys 'name', 'doc', 'params', and 'returns' with deeper keys including 'properties', 'required' and typing keys as necessary.
6. Write the tools.jsonl file for the chatbot agent between <tools> </tools> tags.

In addition to the tools in the policy, consider:
1. The created tools must cover all use cases in the policy. The agent should not be able to perform any concrete action without the use of tools.
2. For instance, if verification is done by sending the user a verification code, make sure there is a tool to send the verification code to the user (after asking the user for their email / phone number) and there is a tool to verify the code the user mentions after.
3. Likewise, all actions that the policy can make the user take must be grounded on the agent's use of tools.
4. Always add an escalation tool, which should be simple and only include a parameter for a summary.
5. Return types must be explicit and simple. Do not use 'returns' as a return type property name.

Do not write the actual code for tools. Only generate the tool specifications in the form of a jsonl.
You must include all tools listed in the original policy.
Ensure that the style, detail, and realism of the generated policy be akin to the reference policies.