Find Element In Frame

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the mutation safety profile. The description adds a useful behavioral trait: 'without global frame state', indicating the tool does not persist or alter frame selection state across calls. However, it does not describe behavior when no element is found or timeout handling; the output schema may cover return values, but the description itself adds limited behavioral context.

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 a single, concise sentence that front-loads the main action and resource: 'Find an element inside a selected iframe/frame without global frame state.' It contains no filler words, is immediately scannable, and every word contributes meaning.

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?

While annotations and output schema cover safety and return values, the description is too terse to fully specify correct usage. The critical gap is how to select the frame (frame_index vs frame_selector, precedence, nesting context). The description does not mention the need to provide a frame selector or index, nor the relationship to sibling tools like frame_list. For a tool with 4 parameters and low schema coverage, this is insufficient for reliable invocation.

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 very low (25%), with only 'selector' having a description in the schema. The tool description does not explain how frame_index and frame_selector work, whether they are alternatives or should both be provided, or which takes precedence. The phrase 'selected iframe/frame' hints at frame selection but gives no parameter-level detail, leaving the agent to guess from names and titles.

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 the tool finds an element inside a selected iframe/frame, with a specific verb ('find') and resource ('element in frame'). The phrase 'without global frame state' distinguishes it from sibling tools that might manipulate global frame context, such as frame_snapshot or element_find in a global context. The title and name align perfectly.

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 implies usage when you need to find an element within a frame without altering the global frame context. However, it does not explicitly mention when to use it versus alternatives like element_find (for current context) or frame_snapshot (for listing frames). No exclusions or alternative tool names are provided, so usage guidance is only implied rather than explicit.

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