browser_iframe_click

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

With no annotations, the description carries the behavioral transparency burden. It communicates that this tool is a shorthand/legacy wrapper and that clicking inside an iframe is its behavior, but it does not disclose failure modes, navigation side effects, or timeout behavior. Some useful context is present, but not comprehensive.

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?

Two short sentences deliver the essential point and the routing guidance without waste. The main purpose is front-loaded, and the preference note is placed in a parenthetical that does not distract.

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?

For a simple legacy click helper, the description plus schema provide enough for an agent to call it correctly: required parameters are clear, purpose is clear, and the preferred alternative is named. It lacks only a deprecation or fallback-behavior note, but this is a minor gap given the tool's simplicity.

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 schema already documents selector and frameSelector with clear descriptions, covering 67% of parameters. The description adds little about parameters beyond framing them in the iframe click scenario. The timeout parameter remains undocumented in both schema and description, preventing a higher score.

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 states a specific action and resource: clicking inside an iframe. It also distinguishes itself from the sibling browser_click by framing itself as a shorthand, and explicitly names browser_click as the preferred alternative.

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 gives clear usage direction: this is a shorthand convenience, while the preferred approach is browser_click with frameSelector. This explicitly tells the agent when to choose another tool over this one.

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