Add instructions for linking to specific tools (#31654)

contributing/content-style-guide.md

@@ -244,6 +244,7 @@ Introduce links consistently using a standard format that clearly indicates wher
 For links to other articles in the GitHub docs: `For more information, see "[Page or article title]()."`
 For links to another section in the same article: `For more information, see "[Header text]()."`
 For links to specific sections in other articles in the GitHub docs: `For more information, see "[Article title]()."`
+For links to an article with a specific tool selected: `For more information, see the TOOLNAME documentation in "[ARTICLE TITLE](/PATH/TO/ARTICLE?tool=TOOLNAME).`
 For links to external documentation: `For more information, see [Page or article title]() in the X documentation.`
 Do not include quotation marks within a hyperlink.
 
@@ -283,6 +284,12 @@ To link to a specific header in the same article, use this format:
 To link to a specific header in a different article, use this format:
 > For more information, see "[ARTICLE TITLE](path-to-article#HEADER-TITLE)."
 
+### Links to a specific tool
+
+When we link to content with a specific tool selected, we want to make sure that someone knows that they will be looking at content relevant to a specific tool even if they do not view the tool switcher tabs in the article.
+
+> For more information, see the TOOLNAME documentation in "[ARTICLE TITLE](/PATH/TO/ARTICLE?tool=TOOLNAME).
+
 ### Links to learning paths
 
 Use this format to link to a learning path.

contributing/tool-switcher.md

@@ -21,9 +21,9 @@ Do not use the tool switcher just to show examples in different languages. Only
 ### How to use tool tags
 Tool tags are Liquid tags that wrap content specific to a tool. For more information on using tool tags in an article, see the [content markup reference](./content-markup-reference.md#tool-tags).
 
-Only include a maximum of eight different tools in an article. Including more tools causes the tool switcher tabs to overflow with an article's table of contents, which prevents people from using either the tool switcher or table of contents. It is unlikely that you will ever need to include eight separate tools in an article. In general, plan to use as few separate tools as possible in an article.
+Put tools in alphabetical order. By default, the first tool tag will be selected for an article. You can define a different default tool for an article in the article's frontmatter. For more information, see the [content README](../content/README.md#defaulttool). You can also link to an article with a specific tool selected by adding `?tool=TOOLNAME` to the end of the link. For more information, see the [content style guide](./content-style-guide.md#links-to-a-specific-tool).
 
-Tool tags are displayed alphabetically. You can define a default tool for an article in the article's frontmatter. For more information, see the [content README](../content/README.md#defaulttool).
+Only include a maximum of eight different tools in an article. Including more tools causes the tool switcher tabs to overflow with an article's table of contents, which prevents people from using either the tool switcher or table of contents. It is unlikely that you will ever need to include eight separate tools in an article. In general, plan to use as few separate tools as possible in an article.
 
 ## Adding new tools
 If a writer determines that adding a new tool is the only way to accurately document something, they should explain their reasoning in the content planning stage. Whoever reviews content plan should consider if there are any alternative ways to address the documentation need without adding a new tool. If a new tool is the only way to create accurate documentation, the new tool should be added. If there is an alternative content solution that does not add a new tool, that option should be used.