find_orphansIdentify notes with no incoming or outgoing links to clean up your Obsidian vault and keep it organized.
List notes with no outgoing or incoming links — useful for vault maintenance.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.6.0Input schema / additionalPropertiesAdded value: +falsev0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate it is read-only and idempotent. The description adds the specific behavior of listing orphans, which is consistent and adds no contradictions.
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?
The description is a single sentence that is entirely front-loaded and contains no fluff or unnecessary information.
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?
For a tool with no parameters and a simple output, the description fully explains its purpose and result, which is complete given the context.
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 are zero parameters, so the description does not need to explain any. Baseline of 4 is appropriate as the schema coverage is 100% and no params exist.
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 clearly states it lists notes with no outgoing or incoming links, and it distinguishes itself from sibling tools like search_notes or get_backlinks which have different purposes.
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?
The description mentions it is useful for vault maintenance, which implies its usage context, but does not explicitly state when not to use or provide alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.