Find Element In Frame

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

Annotations already indicate readOnly, idempotent, non-destructive behavior. The description adds a key behavioral trait: 'without global frame state,' which clarifies it does not alter frame context. This goes beyond annotations.

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 purpose. However, it lacks structural elements like separate sections for usage or parameters, which would improve readability. It is appropriately brief but could be more organized.

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 the presence of an output schema and sibling tools, the description is too sparse. It does not explain how frames are selected, what happens if the frame is missing, or how the tool interacts with frame_list/frame_snapshot. Leaves significant gaps for the agent.

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?

With only 25% schema parameter description coverage (only 'selector' is described), the description adds no parameter details. It does not clarify the roles of 'timeout', 'frame_index', or 'frame_selector', failing to compensate for the low schema coverage.

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, addressing a specific context (frames) that differentiates it from sibling tools like element_find, which operate on the main page. The phrase 'without global frame state' further distinguishes its scope.

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 an element is inside a frame but does not explicitly state when to use this tool versus alternatives like element_find, or how the frame is selected. No guidance on prerequisites or frame selection methods.

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