frame

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

No annotations are provided, so the description must cover behavioral traits. It only mentions two actions without explaining their effects, prerequisites, or error states. For example, what happens if the specified frame does not exist? This is insufficient for a tool that manipulates browser 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 very concise (two sentences) and front-loaded with the core purpose. It could benefit from listing actions in a structured way, but overall it is efficient and avoids unnecessary text.

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 3 parameters, 1 required, and an output schema, the description is incomplete. It does not explain return values, error handling, or how to use the identifier parameter effectively. With no annotations, the description should provide more context for correct 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 0%, meaning param descriptions are missing. The tool description adds only the hint of 'switch' and 'default' for the action parameter but does not explain the 'identifier' parameter (e.g., how to specify a frame by index or name) or 'session_id'. This is minimal compensation for lack of schema descriptions.

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?

Description clearly states the purpose: switching focus to a frame or back to main page. It specifies actions ('switch', 'default'), which helps identify the resource. However, it does not differentiate from sibling tools like 'window' or 'alert', though the frame concept is unique.

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?

Description implies usage context: when you need to interact with a frame. It does not explicitly state when not to use or mention alternatives. The sibling list includes no other frame-specific tools, so the guidance is adequate but not explicit.

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