Perplexity Comet MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the blocking nature and ideal use cases, but lacks details on potential side effects, error handling, or response format. It doesn't mention authentication needs, rate limits, or what constitutes a 'complete response.'

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 and front-loaded: the first sentence states the core functionality, and the second provides usage guidelines. Every sentence earns its place with no wasted words or redundant information.

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's moderate complexity (3 parameters, no output schema, no annotations), the description is adequate but has gaps. It explains the purpose and ideal use cases well, but doesn't address what the response looks like, error conditions, or how it differs from sibling tools. For a tool that interacts with an external service, more behavioral context would be helpful.

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 schema has 100% description coverage, so parameters are well-documented in the schema itself. The description doesn't add any parameter-specific information beyond what's in the schema. The baseline score of 3 reflects that the schema adequately covers parameter semantics without needing description reinforcement.

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 the tool's purpose: 'Send a prompt to Comet/Perplexity and wait for the complete response (blocking).' It specifies the verb ('send'), resource ('Comet/Perplexity'), and behavior ('blocking'). However, it doesn't explicitly differentiate from sibling tools like comet_connect or comet_poll, which likely handle different aspects of Comet interaction.

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 usage context: 'Ideal for tasks requiring real browser interaction (login walls, dynamic content, filling forms) or deep research with agentic browsing.' This gives specific scenarios when to use this tool, but it doesn't explicitly mention when NOT to use it or name alternatives among the sibling tools.

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