hover_by_uid

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

The description adds no behavioral context beyond the annotation readOnlyHint=false. It does not mention that hovering may trigger events, require the element to be visible, or what happens when the UID is invalid. With annotations present, the bar is lower, but this description still fails to disclose any additional operational traits.

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, focused sentence with no extra words or redundancy. It front-loads the core action and is appropriately sized for a simple tool with one parameter.

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 a complete schema and a readOnlyHint annotation, the description lacks any guidance on usage context, potential side effects, or behavior on failure. It is a minimal restatement of the tool's purpose and does not fully equip an agent to decide when or how to invoke it.

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 covers the uid parameter fully with the description 'Element UID from snapshot', and the tool description repeats 'by UID' without adding extra meaning. Since schema_description_coverage is 100%, the baseline is 3, and the description does not enhance parameter understanding.

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's action: 'Hover over element by UID.' This specifies a concrete verb (hover) and resource (element), and it distinguishes itself from sibling tools like click_by_uid, fill_by_uid, and drag_by_uid_to_uid by the unique action it performs.

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 no explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. It simply states the action, leaving the agent to infer applicability from the tool name and context.

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