pplx_deep_research

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

No annotations provided, so description carries full burden. It discloses the cost (1 deep research query from a limited pool) which is critical. However, it does not mention other behavioral traits like authentication needs, destructiveness, or async behavior.

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?

Two sentences, no wasted words, front-loaded with essential information (purpose and cost). Perfectly concise for the information provided.

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 tool consumes a limited resource and has an output schema, the description fails to describe return values, async nature, or relation to companion tools like pplx_deep_research_start and pplx_research_status. Incomplete for a high-cost tool.

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 coverage is 0%, meaning no descriptions in the schema. The description does not explain the two parameters (query and source_focus) at all, leaving the agent to infer from names only. This is a significant 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 produces in-depth reports via deep research, and explicitly limits usage to when the user requests deep research. However, it does not differentiate from related siblings like pplx_deep_research_start or pplx_research_status, which may cause confusion.

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?

Provides clear directive 'Only use when the user explicitly requests deep research' and mentions cost constraints. Lacks explicit alternatives or when-not-to-use scenarios, but the instruction is strong enough for most cases.

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