webview_dom_snapshot

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

Annotations already mark readOnlyHint=true, and the description adds rich behavioral context: it requires an active driver session, explains app targeting defaults, details selector strategies and fallbacks, and describes output formats (YAML with roles/names/states for accessibility, tags/IDs/classes for structure). No contradiction.

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 appropriately sized and front-loaded with the core purpose. Every sentence adds value, though it could be slightly more concise without losing information.

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?

Despite no output schema, the description compensates by detailing the YAML output structure for both snapshot types. It covers all parameters, prerequisites, targeting logic, and multiple selector strategies, making it complete for the tool's complexity.

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%, baseline 3. The description adds valuable context beyond schema, such as explaining the difference between snapshot types and how selector strategies work (fallback to placeholder, aria-label, etc.), earning a score above baseline.

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 starts with a specific verb+resource: "Get a structured DOM snapshot of a Tauri app's webview." It clearly distinguishes two snapshot types (accessibility and structure) with specific use cases, and the tool's purpose is distinct from siblings like webview_find_element.

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 explicit use cases for each snapshot type (e.g., "understanding UI semantics, finding interactive elements, or accessibility testing") and notes prerequisites (requires active driver_session). However, it does not explicitly state when not to use or compare with alternatives.

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