webmcp-tool-annotations

Implement WebMCP tool annotations for browser permission prompts and agent behavior.

35|16|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/OrcaQubits/agentic-commerce-claude-plugins --skill webmcp-tool-annotations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webmcp-tool-annotations
Source: https://github.com/OrcaQubits/agentic-commerce-claude-plugins/tree/main/webmcp-browser-agents/skills/webmcp-tool-annotations
Command: npx skills add https://github.com/OrcaQubits/agentic-commerce-claude-plugins --skill webmcp-tool-annotations

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps developers and agents understand and implement safety annotations for browser-based tools, ensuring secure and user-friendly interactions by informing permission prompts and agent behavior.

Core Features & Use Cases

  • Define Safety Hints: Implement readOnlyHint, destructiveHint, and idempotentHint to guide browser security.
  • Inform User Prompts: Ensure users are appropriately prompted before sensitive actions.
  • Use Case: When creating a new tool for an e-commerce agent, use this Skill to correctly annotate placeOrder as destructive and searchProducts as read-only, ensuring the browser prompts the user before checkout but allows product searches without interruption.

Quick Start

Use the webmcp-tool-annotations skill to implement readOnlyHint and idempotentHint for the searchProducts tool.

Frequently Asked Questions about webmcp-tool-annotations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are WebMCP tool annotations and how do they affect browser permissions?

WebMCP tool annotations are safety metadata hints like readOnlyHint, destructiveHint, and idempotentHint that inform browser permission prompts and guide agent behavior during agentic browser interactions. They ensure users are appropriately prompted before sensitive actions occur.

How do I mark a browser tool as read-only or destructive for an AI agent?

To mark browser tools for an AI agent, implement safety annotations by applying readOnlyHint for non-mutating actions like searchProducts, or destructiveHint for sensitive operations like placeOrder. This ensures the browser prompts the user before checkout but allows searches without interruption.

When should I use idempotentHint when annotating browser tools?

Use idempotentHint when annotating browser tools that can be safely repeated without changing the result beyond the initial application. Combining it with readOnlyHint or destructiveHint requires understanding potential annotation combinations to effectively enhance security and user experience in agentic browser interactions.

Do I need specific dependencies to implement safety hints for browser-based tools?

No specific dependencies are required to implement safety hints for browser-based tools. You only need an understanding of annotation types, browser usage contexts, and potential combinations to effectively apply readOnlyHint, destructiveHint, and idempotentHint for secure agentic browser interactions.

What is the best way to configure browser permission prompts for e-commerce agent tools?

The best way to configure browser permission prompts for e-commerce agent tools is to use WebMCP tool annotations. Correctly annotate placeOrder as destructive and searchProducts as read-only to inform browser security, ensuring the browser prompts the user before sensitive checkout actions.