switch_frame

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

The description adds value beyond annotations by stating that changes persist, there is a 5-second wait, and the operation is browser-specific. Annotations already provide idempotentHint and destructiveHint, so the description complements well.

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 three sentences, front-loaded with the main action, and contains no unnecessary information. Every sentence serves a purpose.

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?

Given a single parameter and no output schema, the description covers all key aspects: behavior, persistence, timeout, and browser scope. It is complete for a simple frame-switching tool.

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 coverage is 100%, with the parameter description already covering CSS/XPath selector and omission behavior. The tool description reinforces this and adds behavioral context (persistence, timeout), but does not provide new semantic details beyond schema.

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 switches WebDriver frame context into an iframe by CSS/XPath selector, or back to top-level if selector omitted. It distinguishes from sibling tools like switch_context and switch_tab by specifying 'frame context' and 'browser-only'.

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 says 'Browser-only' and explains that changes persist for subsequent commands until switching back. It implies when to use (interact with iframe content) but does not explicitly state when not to use or provide alternatives. The guidance is clear but not exhaustive.

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