> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/agent-workspace-documentation/planner-agent/planner-agent-search-tips.md).

# Planner Agent search tips

## Planner Agent search tips

Planner Agent uses meaning-based search to find relevant test cases.

It does not rely only on exact keyword matches.

<figure><img src="/files/ybmUYSqZPjDH022vsUcc" alt="" width="375"><figcaption></figcaption></figure>

### How search works

When you describe a feature or journey, Planner Agent looks for related terminology and matching test coverage in your current project.

This helps it find useful results even when your wording differs from the wording used in existing test cases.

For example, a request for `Login` may also match related authentication flows.

A request for `Fund Transfer` may also match related transfer methods already described in the repository.

### Choose a better query

<figure><img src="/files/rdisecbCbPpJwUxbv02n" alt=""><figcaption></figcaption></figure>

Use a clear feature, journey, or release area.

Good examples include:

* `UPI payments`
* `Payment checkout flow`
* `Password reset`

Avoid vague prompts such as `yes`, `ok`, or short follow-up messages without enough context.

### Result limits

Planner Agent lets you choose how many test cases to return before you run the search.

Use a lower number when you want a focused shortlist.

Use a higher number when you want broader plan coverage.

If the results feel too narrow, raise the limit and search again.

### No-result searches

If nothing relevant is found, Planner Agent returns zero results instead of inventing test cases.

This usually means one of these things is true:

* the current project does not contain matching coverage
* the search should be rewritten with a clearer feature or journey name
* the search is being run in the wrong project

### Common pitfalls

* Do not combine multiple unrelated requests into one search if you want separate result sets.
* Do not assume a missing result means the test case does not exist. It may be stored in a different project.
* Do not expect Planner Agent to create new test cases. It only finds and organizes existing ones.

### Next step

Return to [Planner Agent](/appx_documentation/agent-workspace-documentation/planner-agent/overview.md) for the end-to-end workflow.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mozarkdocs.gitbook.io/appx_documentation/agent-workspace-documentation/planner-agent/planner-agent-search-tips.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.