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 adds some context about the auto-start feature, which is useful beyond just the basic action. However, it doesn't cover other important behavioral aspects such as error handling, timeout behavior, or what happens if the browser is already connected, leaving gaps in transparency.

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, consisting of a single, clear sentence that directly states the tool's purpose and key behavior. Every word earns its place, with no wasted information or 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?

Given the tool's complexity (simple connection action with 0 parameters) and the lack of annotations and output schema, the description is minimally adequate. It covers the main action and an important behavioral detail (auto-start), but it doesn't provide complete context such as what 'connected' means operationally or any error scenarios, which could be helpful for an agent.

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 tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately focuses on the tool's action. A baseline of 4 is applied since no parameters exist, and the description doesn't attempt to explain non-existent parameters.

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 with a specific verb ('Connect') and resource ('Comet browser'), and it adds valuable context about auto-starting behavior. However, it doesn't explicitly differentiate this tool from its siblings (like comet_ask or comet_tabs), which would require a perfect score.

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 implies usage context by mentioning 'auto-starts if needed,' suggesting this tool should be used when establishing a connection to the browser. However, it doesn't provide explicit guidance on when to use this versus alternatives (e.g., whether to use comet_connect before other tools or if it's optional), nor does it mention any exclusions or prerequisites.

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