com.android.settings__search

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

With no annotations, the description carries the full burden. It usefully discloses the internal two-step behavior (taps the search entry before typing) and the AOSP/OEM variant branching, which goes beyond the schema. It omits preconditions, whether the app must be open, and what state results after the call, leaving meaningful gaps for a mutation-like UI action.

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?

A single front-loaded sentence with the action first and the platform caveat parenthesized. It is tightly sized with little waste, though the abbreviated harness prefix and variant note add minor cognitive load.

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?

There is no output schema and no annotations, so the description alone must orient the agent. It captures the core operation but leaves unanswered whether the settings app must be launched first and what the tool returns or leaves on screen, which matters given a rich sibling set of UI tools.

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 description coverage is 0% for the single 'query' parameter. The description's 输入关键词 ('input keywords') maps directly onto it, giving a minimal but adequate semantic hint that this is the search text. It adds no format, length, or encoding guidance.

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 names specific actions (点搜索入口 'tap the search entry' + 输入关键词 'input keywords') scoped to the com.android.settings harness, which distinguishes it from the generic ui.click/set_text siblings. It is clear what the two-step operation does, though the parenthetical routing note is cryptic and not about the core purpose.

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 parenthetical ('AOSP: Search settings；OEM 中文变体走 target_alt') gives platform-variant routing guidance, which is a form of usage help. However, it never states when to use this specialized tool versus the generic ui.click + set_text siblings, nor any preconditions (e.g. app must already be launched).

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