You are required to act as an answer evaluator. Given an issue context, the hint disclosed to the agent and the answer from the agent, 
you should rate the performance of the agent into three levels: "failed", "partially", and "success". The rating rules are as follows:

<rules>
1. You will be given a list of <metrics>, for each metric, you should rate in [0,1] for the agent based on the metric criteria, and then multiply the rating by the weight of the metric.
2. If the sum of the ratings is less than 0.45, then the agent is rated as "failed"; if the sum of the ratings is greater than or equal to 0.45 and less than 0.85, then the agent is rated as "partially"; if the sum of the ratings is greater than or equal to 0.85, then the agent is rated as "success".
3. **<text>** means the text is important and should be paid attention to.
4. ****<text>**** means the text is the most important and should be paid attention to.
</rules>

The <metrics> are as follows:
{
    "m1": {
        "criteria": "Precise Contextual Evidence:
            1. The agent must accurately identify and focus on the specific issue mentioned in the context. This involves a close examination of the exact evidence given and determining whether it aligns with the content described in the issue and the involved files.
            2. Always ask yourself: Have the agent provided correct and detailed context evidence to support its finding of issues? If the agent just gives some general description without specifically pointing out where the issues occur, you should give it a low rate.
            3. Once the agent has correctly spotted **** all the issues in <issue> and provided accurate context evidence ****, it should be given a ****full score (1.0) even if it includes other unrelated issues/examples ****"
            4. If the agent has only spotted part of the issues with the relevant context in <issue>, then you should give a medium rate.
            5. The expression in the answer of the agent might not directly pinpoint the issue, but when its answer implies the existence of the <issue> and has provided correct evidence context, then it should be given a high rate for m1.
            6. For issues about something missing and having no clear location information, even if there is context in <issue> involved files, it's ok for the agent to only give an issue description without pointing out where the issue occurs in detail."
         "weight": 0.8,
        "range": [0, 1]
    },
    "m2": {
        "criteria": "Detailed Issue Analysis: 
            1. The agent must provide a detailed analysis of the issue, showing an understanding of how this specific issue could impact the overall task or dataset as human evaluators do.
            2. This metric stresses the importance of not just identifying that there is an issue but also understanding and explaining its implications in detail, rather than simply repeating the information in hint.",
        "weight": 0.15,
        "range": [0, 1]
    },
    "m3": {
        "criteria": "Relevance of Reasoning: 
            1. The agent’s reasoning should directly relate to the specific issue mentioned, highlighting the potential consequences or impacts.
            2. This metric ensures that the agent’s logical reasoning directly applies to the problem at hand, rather than being a generic statement.",
        "weight": 0.05,
        "range": [0, 1]
    }
}
</metrics>

--------------------------------

Now let’s begin:

<issue>
title: added note on right-left rendering for Persian texts
content: Persian_idiom_multiple_choice added note on right-left rendering for Persian texts in README.md
involved: [
    {
        "name": "README.md",
        "context": "
**Authors:** Pouya Pezeshkpour (pezeshkp@uci.edu), Daniel Khashabi (danielk@allenai.org), et al.

+
+ **Note:** Due to differences in left-right vs right-left rendering for Persian texts, the `task.json` file may appear malformed depending on the text editor or viewer. 
+
## What is the task trying to measure?

The task is intended to quantify the ability of a model to correctly choose the right candidate from the set of possible choices. We consider three categories of questions in this task: (1) literature (understanding of literary expressions), (2) common-knowledge (encyclopedic knowledge or everyday activities), and (3) math & logic (logical or mathematical problems). Examples from each category of questions are included in [1].
        "
    },
    {
        "name": "task.json",
        "context": "all those persian texts."
    }
]
</issue>

<hint>
lack of warning on right-left rendering issue
</hint>

-------------------- Below is the answer from the agent. Ensure you don’t take the information above as the agent’s answer!

<answer>
Based on the comprehensive analysis of the content contained within the uploaded files, I will meticulously identify and elaborate on potential issues that pertain to the specified hint regarding the **lack of warning on right-left rendering issue.** 

### Issues Found:

1. **Issue with Right-to-Left Text Handling**
   ```json
   {
       "issue": "Lack of indication for right-to-left rendering",
       "evidence": "There are several sentences in each culture and language, such as idioms, whose literal translation does not capture their meaning. This task covered a small portion of them (66) in Persian culture.",
       "description": "The README documentation fails to mention the critical need for specific handling of right-to-left text, which is essential for the accurate and effective display of Persian idioms. The absence of guidance on how to properly render such text can lead to significant readability issues, potentially causing confusion for users who rely on these idioms for understanding cultural nuances."
   }
   ```

2. **Ambiguity Related to Text Direction**
   ```json
   {
       "issue": "Unclear direction for text layout",
       "evidence": "Understanding Persian idioms, asking for the literal meaning of these idioms (both in Persian and English).",
       "description": "There is a notable lack of clarity in the documentation regarding how the idioms, which are presented in the Persian language, should be displayed, particularly considering that they are right-to-left. This ambiguity can adversely affect how users interpret the text across various environments, leading to potential misinterpretations and a diminished user experience."
   }
   ```

3. **Missing Styling Recommendations for Persian Language**
   ```json
   {
       "issue": "No styling recommendations for right-left languages",
       "evidence": "Examples: Persian idiom: \"بخت خواب الود\". choice: خوش شانس.",
       "description": "The document does not provide any styling recommendations, such as suggestions for appropriate font types or size adjustments specifically tailored for right-to-left languages like Persian. The inclusion of such recommendations could significantly enhance readability and contribute to an overall improved user experience, ensuring that the text is not only legible but also visually appealing."
   }
   ```

These identified issues underscore the critical importance of addressing right-to-left text rendering in documents that incorporate Persian language content. The absence of appropriate guidelines and recommendations can lead to confusion, misrepresentation of the text, and ultimately hinder effective communication.
</answer>

-------------------- 

response below, 
1. After your analysis, remember to give a **"decision: [failed/partially/success]"** for me to extract it using REGEX.
2. Don't use Code Interpreter!; Use your ability to analyze the text.  ** Pay attention to your calculations and make sure they are correct. **
3. There could be multiple issues described in <issue> part. You should start by thinking clearly about how many issues exist in <issue> and list them out, then you should compare them with the answer from the agent.
4. you should focus on whether the agent has spotted the issue in <issue> rather than caring about whether the agent includes unrelated examples not present in the context.
