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 of behavioral disclosure. While it lists action types, it doesn't describe what happens during execution (e.g., whether it waits for elements, handles errors, or has side effects). For a complex interaction tool with 7 parameters, this leaves critical behavioral traits undocumented, though it doesn't contradict any annotations.

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—a single sentence listing key actions with 'etc.' to imply broader capabilities. It's front-loaded with the core purpose and wastes no words. Every part of the description earns its place by communicating essential functionality 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 (7 parameters, no annotations, no output schema) and the presence of many sibling tools with overlapping functions, the description is inadequate. It doesn't explain return values, error conditions, or how it differs from specialized siblings. For a general-purpose interaction tool in a crowded namespace, more context is needed to guide proper usage.

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 7 parameters thoroughly with descriptions and enums. The description adds no parameter-specific information beyond implying the 'action' parameter through its examples. This meets the baseline of 3 when schema coverage is high, but doesn't provide additional semantic context.

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: 'Interact with elements' followed by specific action examples (click, type, upload files, select options, etc.). It uses a verb+resource pattern and lists concrete actions, making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like cdp_click_coordinates or cdp_type_text, which appear to offer overlapping functionality.

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 no guidance on when to use this tool versus alternatives. With multiple sibling tools that seem related (e.g., cdp_click_coordinates, cdp_type_text, cdp_submit_form), there's no indication of when this general-purpose interaction tool is preferred over more specialized ones. The description only lists capabilities without context for selection.

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