switch_to_frame

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

No annotations are provided, and the description does not disclose behavioral details like what happens to the previous context, error cases (e.g., iframe not found), or requirements (e.g., frame must exist). The impact of switching focus is not elaborated.

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 consists of two concise sentences with the main action front-loaded. It contains no redundant information and is efficiently worded.

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 the tool has 5 parameters, no output schema, and no annotations, the description is too brief. It lacks context about post-switch behavior, switching back, error handling, and the relationship to sibling tools.

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 60% (index, name, selector have descriptions; by and timeout lack descriptions). The description adds value by grouping the three locator parameters and clarifying their types, but does not explain 'by' or 'timeout' parameters, leaving gaps.

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 action ('Switch focus into an iframe') and specifies the possible inputs (index, name/id, selector), distinguishing it from sibling tools like 'switch_to_window' and 'switch_to_default_content'.

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 when to use the tool (when needing to interact with an iframe) but does not explicitly state conditions or alternatives, such as when to use 'switch_to_default_content' or how to handle multiple iframes.

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