ruyi_dom_select

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

Without annotations, the description carries the full burden of disclosure. It adds useful selector format examples but does not explain the return value, error behavior when the element is not found, or whether the timeout parameter triggers a wait. The timeout is present in the schema but its behavioral implication is not described.

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 plus a compact format list. It is front-loaded with the core purpose and contains zero wasted words.

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 there is no output schema, the description should explain what the tool returns (element information, handle, etc.) and what happens if the selector does not match. It also leaves pageIdx unexplained. For a tool used to locate elements for subsequent interactions, this is a significant gap.

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 description supplements the schema with concrete selector format examples (e.g., '#id', 'css:.class', 'xpath://div'), which adds meaning. However, the pageIdx parameter has no description in either schema or description, and the timeout behavior is only implied. Schema coverage is 67%, so the description provides some but not full compensation.

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 locates DOM elements in the page, which is a specific verb+resource. It lists multiple selector formats, making its role as a locator distinct from action-oriented siblings like ruyi_dom_click or ruyi_dom_input, but it does not explicitly differentiate itself.

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?

No guidance is given on when to use this tool versus other DOM tools (ruyi_dom_get_info, ruyi_dom_click, etc.). The description implies it is for locating, but does not clarify that it should be used before actions or how it relates to alternatives.

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