Lean and dense — a single-sentence definition plus tight bullet directives, with no padding about what intentions/libraries are; every line adds domain-specific guidance Claude would not already know.

Provides concrete, executable guidance throughout — named MCP tools (e.g. `mps_mcp_insert_root_node_from_json`, `mps_mcp_check_root_node_problems`, `mps_mcp_apply_intention`) with parameters, exact concept FQNs, and a numbered workflow with copy-ready commands.

The Common-Path Workflow is a clearly sequenced six-step process with an explicit validation checkpoint in step 6 (`mps_mcp_check_root_node_problems`, rebuild, then headless confirmation via `mps_mcp_list_node_intentions`), plus a Critical Directive reinforcing validate-before-test.

The body is an overview with a well-signaled Reference Index pointing to seven real one-level-deep `references/*.md` files (all present, none further nested), each prefaced with a precise 'Open ... when' trigger so navigation is unambiguous.

Names multiple concrete actions — 'adding IntentionDeclaration roots, parameterized or surround-with variants, description/isApplicable/execute blocks, child-filter functions, factory-initialized AST splicing' — rather than vague language.

Explicitly answers both what (the listed authoring actions) and when via an opening 'Use when defining or editing MPS intentions ... or debugging why an intention is not offered' trigger clause.

Covers natural terms an MPS user would actually say — 'MPS intentions', 'Alt+Enter context-action', 'IntentionDeclaration', 'intention is not offered' — rather than abstract jargon.

Scoped to a clear niche — the MPS intentions aspect living in the `intentions` model using `jetbrains.mps.lang.intentions` — making it unlikely to trigger for sibling aspects like actions or constraints.