834 B
834 B
name, description, when_to_use, when_not_to_use, success_criteria
| name | description | when_to_use | when_not_to_use | success_criteria |
|---|---|---|---|---|
| Traverse | Gather deeper context by traversing connected nodes before answering. | Question benefits from broader context than a single direct lookup. | Simple factual answer can be resolved from one direct node. | Answer is grounded in relevant connected context without over-traversal noise. |
Traverse
Strategy
- Start with seed nodes from the user query.
- Expand neighbors breadth-first with depth limits.
- Prioritize high-signal nodes (strong relevance + strong edge semantics).
- Pull key evidence from top nodes.
- Answer directly and explain why chosen nodes mattered.
Defaults
- Depth: 2
- Seed count: 3-5
- Exploration budget: ~40 nodes
Do Not
- Traverse without limits.
- Include distant low-signal nodes just to add volume.