# Evaluating documentation

Documentation, like that of open source and private packages, in the registry show evaluation scores that tell you whether that documentation actually improves agent code quality.

## TL;DR

Documentation provides information on how to use open source or private libraries.

By publishing a tile with documentation for an open source or private library, an evaluation will be performed to determine how effective the documentation is. For example:<br>

* The Tessl registry has documentation for express\@v5.1.0, the evaluation will determine how well tasks are performed by an agent with and without the v5.1.0 Tessl tile.

## What evaluations measure

Evaluations test agents on real tasks with and without documentation:

* Does the agent use correct APIs?
* Does the agent follow best practices?
* Is the code maintainable?

For example: Without docs, an agent might use `http.createServer()` directly. With good docs, it uses Express's `app.listen()` - the intended API.

## Viewing evaluation results

In the [Tessl Registry](https://tessl.io/registry), evaluation results show:

* How much a tile improves agent accuracy
* Which tasks it helps with
* Whether it's worth installing for your use case

Use these scores to choose tiles that will actually help your team.

## Requesting evaluations

Need documentation for a public package that doesn't have coverage yet?

1. Visit the [Tessl Registry](https://tessl.io/registry)
2. Request an evaluation for that package

## Creating evaluated tiles

When you create and publish documentation, they can be evaluated:

```bash
# Create documentation
tessl tile new --name myworkspace/my-library-docs --docs

# Write your documentation
# Edit docs/index.md with structured guides

# Publish
tessl tile publish
```

Published tiles are evaluated to show their impact on agent accuracy.

## Next steps

* [Evaluating skills](/evaluate/evaluating-skills.md) - Skill evaluation scores
* [Creating documentation](/create/creating-documentation.md) - Write tiles
* [Autogenerating documentation](broken://pages/igFZovBVTWCexNCUgNsz) - Generate docs

## Related

* Blog: [How documentation improves agent accuracy](https://tessl.io/blog/fixing-api-misuse-how-tessl-improves-agent-accuracy-by-up-to-33x/)
* [Tessl Registry](https://tessl.io/registry) - Browse evaluated tiles
* [Glossary: Evaluations](/reference/glossary.md#evaluations-evals)


---

# 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.tessl.io/evaluate/evaluating-documentation.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.