focus

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

No annotations are provided, and the description gives no behavioral details. It does not mention side effects, error handling (e.g., if element not found), whether it triggers events, or if it scrolls the element into view.

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?

While very short (one sentence), the description is under-specified rather than concise. It lacks structure such as separating purpose from usage or parameter details, making it unhelpful for an AI agent.

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?

Despite having only one parameter and an output schema (not shown), the description fails to cover needed context. It doesn't describe return values, error scenarios, or typical usage, leaving the agent with insufficient information.

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 has 0% description coverage for the single parameter 'selector'. The description does not explain what format the selector should be (CSS, XPath, text), adding no meaning beyond the schema's basic type.

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 'Focus an element' is a verb+resource but lacks context. It does not specify what 'focus' means in a browser automation context (e.g., keyboard focus, visual focus), and it fails to distinguish from similar operations like click or hover among many siblings.

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 provided on when to use this tool. There are no instructions about prerequisites, when to prefer focus over alternatives (e.g., click, scroll_to), or typical use cases (e.g., before typing).

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