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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the agent knows this changes state but is not destructive. The description adds real value by clarifying that focus does not insert content, but it does not say what focusing actually does (keyboard focus vs scroll-into-view) or what happens if the element is absent or ambiguous. Adequate, not rich.

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 tight sentences, front-loaded with the intended action and followed immediately by the exclusion and the redirect to the alternative. Zero filler.

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?

The tool has an output schema and full parameter documentation, so return values and argument meanings are covered elsewhere. What remains the description's job — what the tool does, when to use it, what it does not do, and which sibling to use instead — is all present.

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 100%, so all nine parameters are already documented in the schema, and the description only restates the selector/text targeting choice. Baseline 3 applies since the schema carries the parameter burden; the description adds no syntax, precedence, or targeting-edge-case guidance.

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?

Specific verb (focus) plus a precise resource (a specific existing Chromium page element), with both targeting mechanisms named (CSS selector or text). It also separates itself from the nearest sibling by stating 'prefer browser_find for an unknown target', so an agent can route between them without opening either schema.

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?

Gives a clear use context ('before typing'), an explicit exclusion ('It does not enter content'), and names the alternative for the unknown-target case. It does not address overlap with other element-targeting siblings such as browser_scroll_into_view or browser_click, but the primary ambiguity is resolved.

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