pplx_deep_research_start

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

No annotations are provided, so the description carries full burden. It discloses asynchronous behavior, immediate return of task_id, and cost of 1 deep research query. It does not mention error handling, permissions, or rate limits, but the core behavioral traits are covered for a simple async start tool.

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?

Three sentences, each carrying essential information: action, cost/alternative, and follow-up. No unnecessary words. Key points are front-loaded. Highly efficient.

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?

The tool is simple (2 params, no nested objects, has output schema). The description covers purpose, async return, and cost. It lacks details on the source_focus parameter and any limits on concurrent tasks, but for an async start tool, the core information is present. Output schema existence reduces the need to describe return values.

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?

Schema has two parameters (query, source_focus) with 0% description coverage. The description does not add any meaning beyond the parameter names. The parameter names are self-explanatory, but the description fails to provide context like valid values for source_focus or example queries, leaving a gap.

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 deep research task asynchronously, distinguishes from sibling pplx_deep_research by noting this avoids timeouts for complex queries, and specifies it returns a task_id immediately. The verb 'start' and resource 'deep research task' 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?

Explicitly says 'Use this instead of pplx_deep_research for complex queries to avoid connection timeouts.' Provides clear guidance on when to use this tool vs the alternative. Also tells the agent to poll pplx_research_status with the task_id to get the result, which is direct usage help.

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