Start Async Search

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true and destructiveHint=false, confirming non-destructive behavior. The description adds that the search runs asynchronously and returns a search ID, which is crucial for tool invocation flow.

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?

Description is front-loaded with the core purpose, uses structured sections (Args, Returns, Example) for easy scanning, and every sentence adds value. No redundancy with schema or annotations.

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?

Given the simplicity (2 required params, no output schema), the description fully covers what an agent needs: how to start, get results, and stop. Sibling tools provide necessary context for alternatives.

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?

Input schema already covers both parameters with descriptions (100% coverage). The description provides an example value ('C:\Users', '*.pdf') that clarifies wildcard usage. Since schema coverage is high, baseline is 3, and the example pushes it to 4.

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 starts a background search, distinguishing it from synchronous search (fc_search_files) by emphasizing asynchronous behavior. The verb 'starts' and resource 'background search' are specific.

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 explicitly frames usage: use this for background search, then get results with fc_get_search_results or stop with fc_stop_search. It includes an example showing the sequence, and siblings imply alternatives (fc_search_files for synchronous).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.