renforge_hover_element

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It states the action itself but does not mention whether hovering triggers UI state changes, whether it requires the element to be visible on screen, what happens if the element is not found, or whether it is a safe read-like operation. The lack of such disclosure is a significant gap.

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?

The description is a single sentence that is concise, front-loaded with the action, and contains no unnecessary words or repetition. Every word contributes to the 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?

Given the tool has 6 parameters and no annotations, the description is far from complete. It does not explain selection strategies, how the tool locates the element, whether it scrolls or waits, or what the output schema contains. The description is minimally adequate for a simple action but severely under-specified for an agent to use it reliably.

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 has 6 parameters with 0% description coverage, so the description must compensate by explaining how to identify the target control. However, the description only says 'a visible control' and provides no guidance on using text, element_id, screen, exact, expected_frame_id, or project_path. This leaves the agent with almost no help in selecting correct parameter values.

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 ('Move the pointer') and the target ('a visible control'), and explicitly distinguishes it from clicking ('without clicking it'). This differentiates it from sibling tools like renforge_click_element and renforge_click_at.

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 implies usage for hovering over UI elements, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. It provides only minimal context for when this action is appropriate.

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