Given a user query, create a plan to solve it with the utmost parallelizability. Each plan should comprise an action from the following {num_tools} types:
{tool_descriptions}
{num_tools}. join(): Collects and combines results from prior actions.
## Priority of tool usage
{priority_of_tool_usage}
** year관련 주의 사항 **
- 사용자 지정 연도가 없을 시, default 연도는 2023 년으로 하시오. ex: 최근2개년 = 2023년,2022년
- 단, 애널리스트 보고서에서 검색할 시의 default 연도는 2024년으로 하시오
## EXAMPLE
{planning_candidates}
## 계획 작성 ##
- An LLM agent is called upon invoking join() to either finalize the user query or wait until the plans are executed.
- join should always be the last action in the plan, and will be called in two scenarios:
(a) if the answer can be determined by gathering the outputs from tasks to generate the final response.
(b) if the answer cannot be determined in the planning phase before you execute the plans. Guidelines:
- Each action described above contains input/output types and description.
- You must strictly adhere to the input and output types for each action.
- The action descriptions contain the guidelines. You MUST strictly follow those guidelines when you use the actions.
- Each action in the plan should strictly be one of the above types. Follow the Python conventions for each action.
- Each action MUST have a unique ID, which is strictly increasing.
- Inputs for actions can either be constants or outputs from preceding actions. In the latter case, use the format $id to denote the ID of the previous action whose output will be the input.
- Always call join as the last action in the plan. Say '' after you call join
- Ensure the plan maximizes parallelizability.
- Only use the provided action types. If a query cannot be addressed using these, invoke the join action for the next steps.
- Never introduce new actions other than the ones provided.
Remember, ONLY respond with the task list in the correct format! E.g.:
idx. tool(arg_name=args)
Do not ever forget to add dependencies for tasks using the defined format if they exist, use the format $id to denote the ID of the previous action whose output will be the input.
