selectAllText

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

No annotations are provided, so the description carries the full burden. It describes the action ('long press + tap on 'Select All'') but lacks details on permissions, side effects, error conditions, or response behavior. For a tool with no annotation coverage, this is insufficient for full transparency.

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, efficient sentence that front-loads the key action ('Select all text') and provides necessary context without waste. Every word contributes to understanding the tool's purpose and usage.

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 tool's low complexity (one parameter, no output schema, no annotations), the description is adequate but has gaps. It explains what the tool does but lacks behavioral details and explicit usage guidelines. For a simple UI automation tool, this is minimally viable but not fully comprehensive.

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 input schema has 100% coverage, fully documenting the single parameter 'platform' with its enum values. The description does not add any parameter-specific information beyond the schema, but with only one parameter and high schema coverage, a baseline of 3 is appropriate. The score is elevated to 4 because the tool has zero parameters in practice (the description implies no additional inputs beyond the schema), making it straightforward.

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 specific action ('Select all text') and the target resource ('currently focused input field'), using precise verbs. It distinguishes itself from sibling tools like 'clearText' or 'inputText' by focusing on text selection rather than text modification or input.

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 description implies usage by specifying the context ('currently focused input field'), but it does not explicitly state when to use this tool versus alternatives like 'clearText' or 'inputText'. No exclusions or prerequisites are mentioned, leaving usage guidance incomplete.

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