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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly discloses the async fire-and-poll behavior and the terminal states, which is the most important behavioral trait. It does not mention cost, cancellation, or side effects, but the core async contract is well covered.

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 with no filler. The core action, the immediate return value, and the follow-up polling instruction are all front-loaded. Every sentence earns its place.

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 description is sufficient for an agent to call the tool correctly: it identifies the sole required parameter concept (instructions), explains the immediate session_id return, and routes to get_session_status. It does not describe how the final report is accessed beyond polling, but the described contract is reasonably complete for this async 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 100%, so the schema already documents both parameters and the nested settings. The description adds no parameter-level meaning beyond what the schema provides; the baseline of 3 is appropriate.

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 ('Starts'), a clear resource ('the full NeuralVerge AI research workflow'), and distinguishes it from sibling run_* tools by noting it is multi-step search, analysis, and structured reporting. An agent can tell this apart from run_search or the other targeted run_* tools.

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?

It gives clear operational context: the tool is asynchronous, returns a session_id immediately, and should be followed by polling get_session_status until 'complete' or 'failed'. It does not explicitly state when not to use it or name alternatives, so it falls short of a 5.

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