webview_find_element

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

Discloses that it returns the element's HTML, explains fallback behavior for the 'text' strategy (element text content, then placeholder, aria-label, title), and notes that ref IDs work with any strategy. No contradiction with readOnlyHint annotation.

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?

Concise at 5 sentences, front-loaded with purpose, and every sentence adds value. No redundant or extraneous content.

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 tool with 4 parameters and no output schema, the description fully explains behavior, targeting, strategy details, return value, and prerequisites (driver_session). Also provides alternative tool for non-Tauri contexts.

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?

Adds significant meaning beyond the schema: clarifies windowId defaults to 'main', appIdentifier defaults to only connected app, selector interpretation depends on strategy, and details text strategy fallback chain. Schema coverage is 100%, but description enriches each parameter.

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 it finds DOM elements in a Tauri app's webview, specifies supported selector strategies (CSS, XPath, text), and differentiates from sibling tools like webview_dom_snapshot and webview_select_element. The verb 'find' and resource 'DOM elements' are specific.

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?

Explicitly states when not to use: 'For browser pages or documentation sites, use Chrome DevTools MCP instead.' Also provides context on requiring an active driver_session and targeting behavior for appIdentifier, giving clear guidance on proper usage.

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