> For the complete documentation index, see [llms.txt](https://docs.powerall.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powerall.app/en/general/features-and-tags.md).
# Features and Tags
### Characteristics
For Items, Partners and Machines, you can create your own characteristics. But there are also standard characteristics. A characteristic for a machine, for example, is the fuel it uses, as in the image below.
### Tags
You can link so-called 'tags' to many items in Powerall Online. A tag is nothing more than a label that lets you keep certain things together. In the overview screens, you can filter by items with (or without) a certain tag.
How you use this is entirely up to you, but of course there are a number of handy examples to think of. For example, you can link a tag 'Winter service' to all work receipts you created for the winter service, or a tag 'Contractor' to all contractors. By combining multiple tags, you can easily create your own slices.
To create a tag, go to the item you want to link the tag to (for example, a partner) and click 'Add tag'. Here you can choose from existing tags or define a new tag right away.
---
# 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, and the optional `goal` query parameter:
```
GET https://docs.powerall.app/en/general/features-and-tags.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.