Perplexity Comet MCP

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

No annotations are provided, so the description carries full burden. It states the tool stops the task, implying a destructive/mutative action, but doesn't disclose critical behavioral traits: whether this requires specific permissions, if the stop is reversible, what happens to in-progress work, or any side effects. For a tool that halts tasks with zero annotation coverage, 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 a single, efficient sentence that front-loads the core action ('Stop the current agent task') and adds a conditional clause for context. There's zero waste or redundancy, making it highly concise and well-structured.

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 (it stops tasks, implying mutation) and lack of annotations or output schema, the description is incomplete. It doesn't explain what 'stop' entails (e.g., termination, pause, cleanup), the response format, or error conditions. For a tool with potential side effects, more detail is needed.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param details, which is appropriate. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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 action ('Stop') and target ('current agent task'), with the condition 'if it's going off track' providing specific context. It distinguishes from potential siblings like comet_ask or comet_mode by focusing on task termination rather than querying or mode switching. However, it doesn't explicitly differentiate from all siblings (e.g., comet_poll might also affect task flow).

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 when the task is 'going off track', providing some context for when to invoke it. However, it doesn't specify when NOT to use it, mention alternatives (like comet_mode for changing behavior instead of stopping), or clarify prerequisites. The guidance is present but incomplete.

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