# Reviewer Guidelines

### The following guidelines must be adhered to:

#### 1. Understandability

Submissions must be written in English and should be clear and coherent—no gibberish is allowed.

#### 2. Relevance

Content must align with the task topic.

#### Acceptance Example:

**Task**: *Memorable NPCs*

**Acceptable Content:** Lines featuring characters like Jinx from *League of Legends* 

(even though Jinx is not typically considered an NPC).

#### Rejection Example:

**Task**: *Web3*

**Unacceptable Content:** Lines featuring characters like Jinx from *League of Legends*.

#### 3. Optional Questions:

Questions not marked with a red (\*) are optional and do not require review.

These optional fields are intended to provide reasoning for the required fields, and it is by design that there is no “Approve/Disapprove” button for them. This is not a bug.

#### 4. Handling Web Links in Submissions:

If a submission includes a link, reviewers should open it to verify its relevance.

If the link does not work (e.g., a 404 error), the datapoint should be considered poor-quality and disapproved.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.saharaai.com/user-guide-data-services-platform/data-services-page/reviewer-guidelines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.