Ansible project overview

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still adds a genuine behavioral fact beyond them: it never connects to a managed host, which tells the agent there are no side effects or remote auth requirements. It stops short of describing cost or output size, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler. The high-value instruction ('Call it first') is placed after the content list but before the routing clause, and each clause in the enumeration maps to something the tool actually returns.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description compensates by listing the returned categories in detail. Combined with the annotations covering safety and idempotency, an agent has everything needed to decide to call it and to interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single optional parameter and schema coverage is 100% – the schema already documents the ANSIBLE_MCP_DIR / working-directory fallback that the description would otherwise need to supply. The description adds no additional semantics for 'dir', so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a concrete verb-plus-resource framing ('What this Ansible checkout contains and how Ansible sees it') and then enumerates the exact payload: ansible-core version, effective config, collections/roles paths, binaries, playbooks, inventories, roles, requirements files. That enumeration lets an agent separate it from siblings like ansible_config or ansible_collections, which each return a narrower slice.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call it first' states the ordering explicitly, and the parenthetical routes work away from this tool: controller state goes to AAP MCP, actions to ADT MCP. Both the when and the when-not are present, so the agent has a decision rule rather than an inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.