Show CDP setup instructions

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context by explicitly stating that nothing is installed and no browser download occurs, reinforcing the non-destructive, purely informational nature. It goes beyond the annotations by clarifying the actual behavior (prints steps, no side effects).

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?

Two sentences with zero waste. The key message ('Nothing to install') is front-loaded, followed by a clarifying explanation and the concrete action. Every word earns its place.

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?

For a zero-parameter, read-only information tool with no output schema, the description is complete. It tells the agent exactly what the tool does and what it outputs (setup steps). There is nothing missing that an agent would need to call it correctly.

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 tool has zero parameters, so the schema trivially covers 100% of them. The description correctly adds no parameter information because none is needed. A baseline of 4 is appropriate for a parameterless tool.

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 states a specific verb ('Prints') and resource ('exact setup steps'), and immediately clarifies that no installation is needed ('Nothing to install'). This distinguishes it clearly from all browser_* siblings, which are about navigation, interaction, and state management, not setup.

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 that this tool is for obtaining setup instructions, but it does not explicitly state when to use it versus alternatives. There are no similar sibling tools, so the need for differentiation is low, but the description could have mentioned 'Use this when you need to set up CDP connection' for clarity.

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