wavexis_dom_focus

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

Beyond annotations (idempotentHint=true, destructiveHint=false), the description discloses that the tool mutates DOM focus state and may trigger focus event handlers. This adds valuable behavioral context not captured by annotations.

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?

Three sentences with no unnecessary words. First sentence states purpose, second provides usage guidance, third covers side effects and return format. Efficient and front-loaded.

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?

Covers purpose, usage differentiation, side effects, and return. Could mention that focusing may scroll the element into view, but that's a common behavior. Overall quite complete for the tool's complexity.

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 input schema already describes both parameters (selector and session_id) with clear descriptions. The tool description does not add additional meaning beyond mentioning 'CSS selector' implicitly. Schema coverage by the description is minimal, but the schema itself is well-documented, so baseline 3 is appropriate.

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 tool focuses an element via CSS selector. It explicitly distinguishes from wavexis_dom_click by advising use of that tool for activation rather than focus.

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 provides clear guidance on when to use this tool (focusing) versus the alternative (clicking for activation). It does not address other potential alternatives like direct focus via evaluation, but the main distinction is covered.

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