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 mentions viewing and managing tabs but doesn't disclose important behavioral traits: whether this requires browser permissions, what happens when switching/closing tabs (e.g., confirmation prompts), whether changes are reversible, rate limits, or what the response format looks like. For a tool with mutation capabilities (switch/close), this is a significant gap.

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 appropriately sized with two sentences that each serve a purpose: the first states the core functionality, the second explains the value proposition. It's front-loaded with the main purpose. While efficient, it could be slightly more structured by explicitly separating viewing vs. managing aspects.

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 this is a tool with mutation capabilities (switch/close actions), no annotations, no output schema, and 3 parameters, the description is incomplete. It doesn't explain what the tool returns, error conditions, permission requirements, or behavioral implications of the actions. For a tool that can modify browser state, more context is needed about how it behaves and what to expect.

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 all three parameters thoroughly with descriptions and enum values. The description doesn't add any parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 as 'View and manage browser tabs' with specific verbs and resources. It distinguishes from siblings by mentioning tab coordination, but doesn't explicitly differentiate from other browser-related tools (none exist in the sibling list). The description goes beyond the name/title by explaining what information is shown (purpose, domain, status) and the coordination benefit.

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 ('Helps coordinate multi-tab workflows without creating duplicate tabs') but doesn't provide explicit guidance on when to use this tool versus alternatives. There's no mention of when NOT to use it or what specific scenarios warrant its use over other approaches. The guidance is helpful but incomplete.

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