Wait for research

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

Adds context beyond readOnlyHint and openWorldHint: blocking behavior, timeout, return of completed task with results. No contradiction with annotations. Slight gap on timeout outcome but overall good.

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 front-loaded with core action ('block until...') and results purpose. No wasted words, 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?

Coverage adequate for a 2-param tool with annotations: explains purpose, return, and usage flow. Minor omission: no mention of behavior on timeout (incomplete results vs error), but overall completes the picture.

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 covers notebook with description; timeoutSeconds lacks description. Description explains timeoutSeconds meaning as elapse time for blocking, compensating for schema gap. Adds value beyond schema.

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?

Clearly states the tool blocks until a research task completes, with timeout. Specifies return includes completed task and results, and references sibling tools research_import_all/research_import_selected for follow-up, distinguishing purpose from 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?

Informs when to use: to wait for task completion before importing results. Implicitly suggests not using when immediate non-blocking check is desired (research_poll), but lacks explicit when-not or alternative naming.

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