style_hover

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only notes that the menu expands on hover, which is a UI behavior, but does not reveal what the tool does after hovering (e.g., whether it waits, scrolls, or returns a result).

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, concise sentence that front-loads the core action. There is no fluff, but the extreme brevity results in missing details.

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?

With five parameters, no annotations, and no output schema, the one-line description is insufficient for an agent to confidently invoke the tool, especially considering optional parameters and expected behavior.

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 coverage is 60% (index, urlIncludes, titleIncludes have descriptions). The description adds meaning only to 'uid' by indicating it is the hover target, but offers no extra semantics for 'scroll' or the selector parameters.

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 states the specific action '悬停' (hover) and the target 'uid', with a parenthetical clarifying that this is for menus that expand on hover. This distinguishes it from sibling tools like style_click or style_wait, though the meaning of 'uid' is not fully explained.

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?

There is no guidance on when to use this tool versus alternatives such as style_click or style_tabs. The description offers no scenarios, prerequisites, or exclusions.

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