deep_research

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the tool performs search, crawl, and report generation, but does not mention whether it runs asynchronously, how results are returned (e.g., via a job ID), or any side effects or rate limits. Given the existence of sibling tools like start_job and poll_job, the description should clarify these aspects.

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?

The description is a single concise sentence with no filler or repetition. It is front-loaded and easy to parse. However, it is so terse that it sacrifices necessary detail, making it slightly under-specified rather than optimally concise.

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 moderately complex (search + crawl + report) and has no annotation support. Although an output schema exists, the description does not explain the execution model, how to retrieve the report, or whether it uses the job system (siblings include start_job and poll_job). The description is insufficient for an agent to understand the full workflow.

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 description coverage is 0%, so the description must compensate for the lack of parameter documentation. It does not mention the 'query' parameter or the 'timeout_profile' parameter at all. The phrase 'Deep Research' implies the query is the research topic, but this is not explicitly stated, and 'timeout_profile' is entirely unexplained.

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 states a specific verb ('Perform') and resource ('Deep Research') with a parenthetical clarifying that it combines Search, Crawl, and Report. This clearly communicates the tool's core function and distinguishes it from more granular siblings like search_web and crawl_site, though it does not explicitly name those alternatives.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention use cases, prerequisites, or mention sibling tools like search_web or crawl_site for narrower tasks. The usage context is only implied by the name and description.

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