element_longpress

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without detailing what happens after the long press (e.g., duration, side effects, return value, required permissions). This is a significant gap for a gesture-based tool that likely triggers platform-specific behavior.

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 extremely short, but this is under-specification rather than conciseness. It consists of a single phrase that restates the tool name, failing to provide any detail that would help an agent invoke the tool correctly. There is no structure or additional context to aid understanding.

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 low complexity (one parameter, no output schema) the description is minimally adequate, but it leaves critical questions unanswered: what happens after long press, whether the element must be scrolled into view, and what the return value or side effects are. For a tool interacting with a mobile application UI, this is insufficient.

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 one parameter (element_id, string) with zero description coverage. The description implies that element_id is the target element, but it does not explain how to obtain or reference the element, nor does it clarify the expected format or scope. The description adds minimal semantic value beyond the parameter name.

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 '长按元素' ('long press element') is essentially a direct translation of the tool name 'element_longpress' and adds no new information. It states the action and resource but does not distinguish this tool from siblings like element_tap or element_touch, nor does it clarify the effect of a long press.

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 alternative gestures (tap, swipe, touch) or any mention of prerequisites such as element visibility or prior element querying. The description provides no context about typical use cases or scenarios where a long press is appropriate.

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