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. It discloses the polling behavior ('call repeatedly') which is valuable context not in the schema. However, it doesn't mention expected response format, rate limits, authentication needs, or what specific status/progress information is returned. The description adds some behavioral context but leaves significant gaps.

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 perfectly concise with two focused sentences that each earn their place. The first states the core purpose, the second provides crucial usage guidance. No wasted words, well-structured, and front-loaded with the essential 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 this is a monitoring tool with no annotations, no output schema, and 0 parameters, the description provides adequate basic context about purpose and usage pattern. However, for a tool that presumably returns status/progress information, the lack of output description is a notable gap. The description is complete enough for basic understanding but leaves important questions unanswered about what information is returned.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't waste space explaining non-existent parameters. The schema already fully documents the empty parameter set, so no additional parameter semantics are needed or provided.

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 specific verbs ('check', 'monitor') and resources ('agent status and progress', 'agentic tasks'). It distinguishes itself from siblings like comet_stop or comet_ask by focusing on monitoring rather than control or querying. However, it doesn't explicitly differentiate from potential monitoring alternatives in the sibling list.

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 with 'Call repeatedly to monitor agentic tasks', indicating this is for polling/monitoring scenarios. It implies when to use (for tracking ongoing tasks) but doesn't explicitly state when not to use or name specific alternatives among siblings like comet_tabs or comet_mode.

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