webview_select_element

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

Annotations already declare readOnlyHint=true. The description adds useful context: it's interactive, returns an annotated screenshot, and requires a driver session. It does not explicitly mention that the tool blocks waiting for user input with a timeout, though this is captured in the schema. Given annotation coverage, the added value is solid but not complete.

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 concise (four short sentences), front-loads the core action, and avoids extraneous details. Every sentence adds value—scope, requirement, targeting, and return 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?

Despite no output schema, the description covers the return value (element metadata and annotated screenshot), prerequisites (driver session), targeting logic, and the interactive nature. It is complete enough for an agent to understand what the tool does and what to expect.

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%, so the schema already documents all parameters. The description adds minimal extra meaning (e.g., appIdentifier is a port or bundle ID, similar to schema). Baseline score of 3 is appropriate since the description does not significantly augment parameter understanding.

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 activates an element picker overlay for Tauri apps, allowing visual selection and returning rich metadata plus screenshot. It distinguishes from sibling tools like webview_find_element (programmatic) by highlighting the interactive, user-driven nature.

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 specifies that it requires an active driver_session and explains how the target app is selected (default or by appIdentifier). However, it does not explicitly contrast with alternatives (e.g., when not to use it) or state prerequisites beyond the driver session.

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