browser_iframe_fill

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the tool is a shorthand and implies equivalence to browser_fill, but does not mention return values, waiting behavior, errors, or side effects. The core operation is clear, but the behavioral picture is thin.

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 concise sentences with no filler. The core purpose and the preferred alternative are front-loaded, and every clause contributes meaning.

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 alias-like tool, the description is adequate to understand its role and avoid misuse. However, with no annotations and no output schema, behavioral and return details are left unspecified, and the description leans heavily on the recommendation to use browser_fill instead.

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 documents frameSelector and selector, but value and timeout are undocumented, leaving 50% coverage. The description adds no parameter-level meaning beyond what the schema already provides, so it does not compensate for the gap.

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?

States a specific verb and resource: filling inside an iframe. It also explicitly defines itself as a shorthand and points to browser_fill, distinguishing it from browser_iframe_click and other browser tools.

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?

Explicitly instructs the agent to prefer browser_fill with frameSelector, giving a clear alternative and preference. This is direct, actionable usage guidance rather than leaving the choice to inference.

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