deep-search-create-task

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

The description correctly indicates async behavior and immediate return of task_id, which is important. However, with no annotations and no mention of rate limits, error handling, or task lifecycle, the disclosure is adequate but not thorough.

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 extremely concise, consisting of a single sentence. It is front-loaded with the core action. However, it may be too brief, sacrificing necessary detail for brevity.

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 has 2 parameters and no output schema, the description should explain how to construct messages, what model options mean, and what the returned task_id represents. It fails to provide this context.

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%, and the description does not explain any parameters (model, messages). The schema provides enums and defaults, but the description adds no additional meaning or usage guidance for these parameters.

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 creates an async deep search task and returns a task_id immediately. However, it does not differentiate from sibling tools like deep-research-create-task or specify the scope (deep search vs research).

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 vs alternatives like deep-search-sync or deep-research-create-task. There is no mention of prerequisites or post-usage steps such as polling with deep-search-query-task.

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