What are the three core claims Ansible makes about itself: simple, powerful and agentless? What does each mean?

Question

Accepted Answer

Simple: playbooks are human-readable and need no programming skills.
Powerful: covers configuration management, workflow and network automation, the whole application life cycle.
Agentless: nothing to install on managed hosts; Ansible connects over SSH or WinRM.

Claim
What it means in practice

Simple
Playbooks read like a list of instructions. Tasks run in order, top to bottom. Newcomers become productive quickly, and any team can use them.

Powerful
The same tool handles configuration management, workflow automation and network automation, so it can orchestrate an application from deployment through updates.

Agentless
Ansible reaches hosts over OpenSSH (Linux/UNIX) or WinRM (Windows), pushes small programs (modules), runs them and removes them afterwards. You can start almost immediately.

The three reinforce each other: because there is no agent and the language is plain YAML, the barrier to the first useful playbook is very low.
Go deeper:

How Ansible Works (Ansible Collaborative / Red Hat) — official explanation of the agentless model, modules, inventory and plugins.
 Ansible 101 - Episode 1 - Introduction to Ansible (Jeff Geerling) — the best-known free Ansible course, starting from why it is simple.

Claim	What it means in practice
Simple	Playbooks read like a list of instructions. Tasks run in order, top to bottom. Newcomers become productive quickly, and any team can use them.
Powerful	The same tool handles configuration management, workflow automation and network automation, so it can orchestrate an application from deployment through updates.
Agentless	Ansible reaches hosts over OpenSSH (Linux/UNIX) or WinRM (Windows), pushes small programs (modules), runs them and removes them afterwards. You can start almost immediately.