> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/general-naming-conventions/sentence-types.md).
# Sentence Types
Concepts should be names or short noun phrases. Full statements or sentences are unacceptable.
Procedure concepts should not contain phrases that can be categorized as a sentence function type, i.e., imperative, declarative, interrogative, or exclamatory. A procedure description should be a noun phrase that names the procedure, and should not contain information that it was done, or is to be ordered, carried out, or planned.
* For example,
* 11227005 | Excision of ganglion of tendon sheath of hand (procedure)| is a noun phrase giving the proper description for the procedure
* Unacceptable example,
* Hand tendon ganglion excised (situation) indicates the procedure was done, as a past tense declarative statement
This is a situation with explicit context, not a procedure.
Provide Feedback
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/general-naming-conventions/sentence-types.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.