Claim and evidence
Treat MCP tool names, descriptions and example prompts as the main way assistants decide when to use you.
No dated example yet. Treat this tactic as a hypothesis.
Secondary
A reputable third party analysed it (Lenny's Newsletter, First Round Review, Reforge, an Ahrefs study).
Working · 2026-11 Platform guidance from OpenAI and Anthropic; the 'new SEO' analogy is a guest author's framing.
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
Assistants pick tools from their metadata, so clear, narrow and accurate descriptions drive correct use. Directories also review these for accuracy and misleading instructions.
How to run it
- Name each tool for the single task it does
- Write a narrow description stating when to use it
- Avoid generic or single-word names
- Provide example prompts
- Do not instruct the model beyond describing the tool
Ways to run it
Design options to test, not promised results.
- Option AOne task per tool
Split broad tools into narrow ones named for the single job each does.
- Option BWhen-to-use descriptions
Say what the tool does and when it applies, without telling the model how to behave.
- Option CExample prompts
Provide sample user requests that should lead to each tool, and test them in the assistant.
Dated examples
No dated example yet. Treat this tactic as a hypothesis.
Does it still work?
Platform guidance from OpenAI and Anthropic; the 'new SEO' analogy is a guest author's framing. source
Risks
- Descriptions with promotional or behavior-steering text are rejected
- Effect on ranking not quantified
Sources
- lennysnewsletter.com
“As you may have been thinking as you read this, tools also represent a new form of SEO (or is it AEO?).”
✓ quote checked word-for-word on the page - developers.openai.com
“Plugin names and descriptions must be clear, accurate, and straightforward.”
✓ quote checked word-for-word on the page - claude.com
“Describe what the tool does, and don't tell Claude how to behave.”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (ops-ai)