optimai_start_search

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

With no annotations, the description carries the full burden. It discloses that the tool is asynchronous (returns immediately), provides a search ID for polling, and notes the expected search duration. This is strong behavioral context, though it omits details like ID expiration or error conditions.

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 tightly worded sentences. The first states purpose and outcome; the second explains why and what to do next. No filler, all information 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?

For a simple one-parameter async tool, the description covers the key behavioral flow: start, get ID, poll with get_search. It lacks an explicit return field name (e.g., 'search_id') and error-handling notes, but these are minor given the tool's low complexity.

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?

The single parameter 'query' is already well-documented in the schema (100% coverage). The description adds Web3/decentralized context but does not materially expand on the schema's 'The search query to start on the OptimAI network'. Baseline 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 uses a specific verb ('Start'), identifies the resource ('Web3-focused AI search on the OptimAI decentralised network'), and clarifies the immediate outcome ('return immediately with a search ID'). This clearly distinguishes it from sibling tools like optimai_get_search, which fetches results.

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?

The description explicitly states when to use this tool ('searches commonly take 60-90 seconds or the MCP host has short tool-call timeouts') and directs the user to the next step ('Call optimai_get_search with the returned ID'). This provides clear context and a named alternative, satisfying the highest bar.

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