switch_to_frame

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

No annotations and the description omits side effects, error handling (e.g., if selector not found), or state changes beyond 'focus'. Does not mention whether it waits for the frame to load.

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?

Single, clear sentence with no redundancy. The essential information is front-loaded.

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?

Adequate for a straightforward switch action, but lacks details about expected outcomes, potential errors, or return values. Since an output schema exists but is not provided, it's uncertain if return values need explanation.

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?

The only parameter, 'selector', is described as a CSS selector in the text, which adds meaning beyond the bare schema label. This compensates for the lack of parameter description in the 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?

Clearly states the action (switch focus) and target (iframe) with a specific selection method (CSS selector). Distinct from the sibling switch_to_default_content, though it doesn't explicitly contrast them.

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?

Provides no guidance on when to use this tool versus other navigation or frame-related tools. It states what it does but not the context or prerequisites.

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