click_button_by_text

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

With no annotations, the description must fully disclose behavior. It only states 'Find and click a button by its text content' without explaining whether the tool waits for the button to appear, how it handles errors (e.g., button not found), or if the click is instantaneous. The timeout parameter hints at waiting but is not elaborated.

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 with a clear prerequisite marker (red dot). It is concise and front-loaded, but could be structured with bullet points for readability. No 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 the tool interacts with a running game, the description lacks important context: return value (success/failure), error conditions, and detailed behavior (e.g., does it scroll to find the button?). The timeout parameter is not explained, and no output schema exists to compensate.

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% with descriptions for both parameters. The tool description adds no extra meaning beyond the schema; it does not clarify timeout semantics (default, behavior on timeout). Baseline 3 applies as schema already documents the parameters.

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 uses a specific verb ('Find and click') and resource ('button by its text content'), clearly stating the action. It also includes a prerequisite ('Game must be running'), which helps distinguish it from lower-level click tools like simulate_mouse_click.

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 only usage guidance is the prerequisite that the game must be running. It does not explicitly state when to use this tool versus alternatives (e.g., simulate_mouse_click, find_ui_elements) or provide when-not-to-use scenarios, leaving the agent to infer usage context.

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