comet_search

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses the core mechanism (URL-based navigation, waiting time for AI generation, and result extraction) and the mode values. However, it does not mention side effects, failure behavior, external site dependencies, or whether a prior browser connection is required.

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 front-loaded with a one-line purpose, followed by a compact mechanism note and a terse Args list. Every sentence contributes useful information with no redundancy.

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?

An output schema exists, so return-value documentation is not required. The core operation and all parameters are well covered. A minor gap is that prerequisites such as whether an active browser connection via comet_connect must already be established are not stated, but this does not substantially block correct invocation.

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%, but the description compensates fully by documenting all three parameters: query, wait_seconds, and mode, including the exact mode values ('search' or 'research'). This adds real semantic meaning beyond the bare 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?

The description opens with a specific verb-resource pair: 'Search the web using Perplexity via Comet,' and then explains the exact mechanism: navigating to perplexity.ai/search?q=QUERY and extracting the AI-generated results. This clearly distinguishes it from sibling tools like comet_navigate or comet_screenshot.

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 provides clear context: use this tool when an AI-generated web search result is needed, and it explicitly notes that no CSS selectors are required. However, it does not name specific sibling alternatives or state conditions for when not to use it, so it stops 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.