wait_for_window

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

Describes polling behavior and default timeout. With no annotations, description carries full burden; lacks details on timeout behavior (e.g., exception) but covers core polling mechanism adequately.

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?

Concise, well-structured with brief intro and Args section. Every sentence adds value, no fluff.

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?

Covers purpose, parameters, usage context, and polling behavior. Output schema exists so return values not needed. Minor gap: no mention of error on timeout, but overall complete for a waiting tool.

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?

With 0% schema description coverage, description explains all four parameters: title (substring match), app (filter), timeout (max seconds), gone (wait for disappear). Adds meaning beyond names.

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?

Clearly states it waits for a window to appear or disappear. Resource is windows, action is waiting. Distinguishes from siblings like wait_for (general wait) and activate_window (activation).

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?

Explicitly says 'Use after actions that open or close windows.' Provides clear context for when to use, but does not explicitly mention alternatives or when not to use.

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