find_text_on_screen

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

No annotations provided. Description adds case-insensitivity behavior from parameter, but does not disclose limitations (e.g., only visible text, not OCR) or performance characteristics.

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?

Two sentences, zero waste. All information is front-loaded and essential.

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?

No output schema, but description clarifies return format (coordinates). Missing potential edge cases (multiple matches, no match) but adequate for the tool's simplicity.

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 coverage is 100%, so baseline 3. Description reinforces parameter usage (text case-insensitive, app scope) but adds no new semantic details beyond schema.

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?

Description clearly states verb 'Find' and resource 'text on screen', and specifies output as clickable coordinates. Comparison to Ctrl+F helps recognition, but does not explicitly distinguish from sibling click_by_text.

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?

Implies usage via 'use with click_at' and Ctrl+F analogy, but does not explicitly state when to use versus alternatives like click_by_text, or when to use the app parameter.

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