# Machine Readability

## Parser-Friendly Guidelines

1. Limit to 2-3 descriptors per trait
2. Keep descriptions concise
3. Use logical grouping
4. Maintain consistent structure

## How Many Descriptors Are Too Many?

Depends on which LLM you're using, but we'll stick to the general principle of "shorter is better." These thresholds should be taken as general guidelines rather than strict rules.

* **5+ words**: Reduces parsing efficiency
* **7+ words**: Impairs scanning ability
* **10+ words**: Disrupts logical flow

## Format Examples

### **Structure Comparison**

| ❌ **Wrong**         | ✅ **Right**         |
| ------------------- | ------------------- |
| \* name: John Smith | - Name: John Smith; |
| - age:25            | - Age: 25;          |

### **Descriptor Length Comparison**

| ❌ **Wrong**                                                                        | ✅ **Right**                                             |
| ---------------------------------------------------------------------------------- | ------------------------------------------------------- |
| Personality: kind(always helps others no matter what and goes out of their way...) | Personality: kind(puts others first, self-sacrificing); |

<figure><img src="/files/ntrHV2yrs1JlBuyHHwMc" alt=""><figcaption></figcaption></figure>

### TL;DR

Long descriptors risk being ignored. LLMs filter out complex or excessive information as processing noise.

***

![](/files/iadwt1BvQjiz0K1C4cEt)\ <sub>© 2024 by SopakcoSauce. Except as otherwise noted, the content of this page is licensed under</sub> [<sub>CC BY-NC-SA 4.0</sub>](https://creativecommons.org/licenses/by-nc-sa/4.0/)&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://sopakcosauce.gitbook.io/sopakcosauce-docs/plist-sbf-guides/machine-readability.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.