# How to interpret the readability score and metrics.

Your Flensh report includes a readability analysis that scores your content based on several key metrics. A higher overall score indicates your text is clear, direct, and well-structured for machine comprehension.

Key metrics often include:

* **Reading Ease Score:** A score (typically 0-100) where a higher number indicates easier readability. Aim for a score that aligns with a general audience.
* **Grade Level:** An estimate of the level of education needed to understand the text. For most topics, aiming for a grade level between 8 and 10 is a good target.
* **Sentence Complexity:** This looks at the length of your sentences and the use of complex clauses. Shorter, more direct sentences are easier for an AI to process.
* **Passive Voice Usage:** The passive voice can make sentences less direct (e.g., "The ball was hit" vs. the active "John hit the ball"). While not always bad, excessive use can obscure meaning for an AI.


---

# 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://flensh.gitbook.io/flensh-docs/core-features-in-detail/2.5.-the-real-time-readability-analyzer/how-to-interpret-the-readability-score-and-metrics..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.