firefox_focus

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

With no annotations, the description carries full burden. It does not disclose whether focusing scrolls the element into view, requires visibility, or has side effects like changing focus order. The behavior beyond the basic action is unclear.

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 sentence is concise and front-loaded with the key action. No unnecessary words, but could be slightly expanded with additional context without losing conciseness.

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 moderate parameter count (6), the description is too sparse. It does not explain return behavior, success/failure conditions, or how the observe parameter affects the operation. More detail is needed for effective use.

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 description adds meaning by indicating that focusing can be done by selector/ref or via viewport coordinates (x, y). However, the relationship between selector and coordinates is not clarified (e.g., mutually exclusive?). Schema coverage is 50% but the description partially compensates.

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 ('Focus') and the target ('element') and specifies the methods: by selector/ref or viewport point. This distinguishes from sibling tools like click or select_text, though the exact meaning of 'focus' in a browser context is not elaborated.

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?

No guidance on when to use focus versus other actions like click or select_text. No prerequisites or conditions for usage are provided.

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