select_frame

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

No annotations are provided, so the description must fully disclose behavior. It reveals that passing an empty string clears the context, but does not specify error handling (e.g., if frame ID is invalid), side effects, or whether the context persists across calls. Additional traits like requiring frame IDs from list_frames are omitted.

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 two sentences, front-loaded with the purpose, and every word is essential. There is no fluff or redundancy.

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 no output schema and no annotations, the description covers the basic functionality adequately for a simple tool. However, it lacks details on error conditions, prerequisites (e.g., need to list frames first), and how the context interacts with other tools. It is minimally complete but has gaps.

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%, so the description must compensate. It adds value by explaining the clearing behavior with empty string, but does not clarify what a non-empty string should represent (e.g., frame ID, name, or index) or its required format. This is insufficient for correct invocation.

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 ('Set'), the resource ('active frame (iframe) context'), and its effect ('for subsequent tool calls'). It distinguishes from siblings like list_frames by focusing on setting the context rather than listing. The mention of clearing with empty string adds specificity.

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 needing to interact with an iframe, but lacks explicit guidance on when to use versus siblings like select_page or select_worker. No when-not-to-use or alternative recommendations are provided.

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