CDP MCP

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

No annotations are provided, so the description carries the full burden. It discloses that the tool writes to a file (BUGS.md), implying a mutation operation, but lacks details on permissions needed, file overwrite behavior, error handling, or response format. For a mutation tool with zero annotation coverage, this is insufficient behavioral context.

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 concise and front-loaded, consisting of two sentences that directly state the purpose and usage without any wasted words. Every sentence earns its place by providing essential information efficiently.

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 (a mutation operation with no annotations and no output schema), the description is moderately complete. It covers the basic purpose and usage but lacks details on behavioral aspects like error handling or output format. It compensates somewhat with clear usage guidelines, but more context would be beneficial for a mutation tool.

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 100% description coverage, clearly documenting all parameters (title, description, context). The description does not add any additional meaning beyond what the schema provides, such as examples or formatting tips. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 ('Track a bug') and the resource ('in the CDP-MCP'), specifying it writes to BUGS.md in the cdp-mcp folder. It distinguishes from siblings like cdp_fix_bug or cdp_list_bugs by focusing on logging issues rather than resolving or listing them, though it could be more explicit about this differentiation.

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?

It provides explicit guidance on when to use the tool ('when you encounter issues with browser automation'), which is clear and context-specific. However, it does not mention when not to use it or name alternatives like cdp_fix_bug for bug resolution, leaving some room for improvement in sibling differentiation.

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