appium_find_elements

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description goes well beyond them: it specifies the exact return payload, the empty-match contract, that elementId must be reused as elementUUID by interaction tools, and the shouldUseCompactResponses=false prerequisite for elementResponseAttributes drivers.

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?

Three tight sentences, front-loaded with the core behavior and return shape, then interaction hand-off and configuration caveat. No filler or repetition.

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 no output schema, the description compensates by describing the returned JSON structure and the empty-result case, plus how to configure compact responses. Nothing needed to call or consume the result is missing.

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 100%, with rich per-strategy guidance and an enum, so the schema carries the parameter burden and baseline is 3. The description adds only an output-side note about passing elementId as elementUUID, not new input semantics.

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?

States a specific verb and resource ('Find all elements matching a strategy and selector') and explicitly distinguishes itself from appium_find_element by match-count semantics. An agent can select it without opening the schema.

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?

Names the alternative (appium_find_element) with the selecting condition ('when only one match is needed'), and the selector schema routes vision/natural-language lookups to appium_ai action=find_element. Explicit when-not guidance is present.

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