feat: Add destructiveHint and openWorldHint tool annotations #715
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds the missing MCP tool annotations (
destructiveHintandopenWorldHint) to all 26 tools in chrome-devtools-mcp.Changes
ToolDefinition.ts: Added optionaldestructiveHintandopenWorldHintfields to the annotations interfaceopenWorldHint: truefor all tools (browser automation inherently interacts with external websites)destructiveHint: trueforclosePage,navigatePage, andevaluateScript(operations that can cause irreversible changes)destructiveHint: falsefor other write operations (reversible modifications like click, fill, hover)Why These Annotations Matter
Per the MCP specification:
openWorldHint: Indicates tools that interact with an "open world" of external entities. All browser automation tools interact with external websites, so this is true for all tools.destructiveHint: Indicates tools that may perform irreversible updates. This helps AI assistants determine when to request user confirmation.Tools Summary
🤖 Generated with Claude Code