ui_invoke

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

Discloses key behavioral traits: uses UIA InvokePattern, no mouse movement, fallback to Click(). Also notes dependency on debug state. With only openWorldHint annotation, the description appropriately fills in missing behavioral context.

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 front-loaded with purpose and usage guidance, then lists arguments. It is concise but could be slightly more streamlined. Every sentence serves a purpose.

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?

For a UI invocation tool with many siblings and no output schema, the description covers purpose, usage, parameters, and key behaviors. It enables an agent to select and invoke the tool correctly.

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?

Despite 0% schema description coverage, the description provides a brief line for each parameter (automation_id, name, control_type, root_id, xpath), adding meaning beyond the bare property names. However, it lacks precise formats or constraints.

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 'Invoke a UI element using UIA InvokePattern (no mouse movement)' and distinguishes itself from sibling ui_click by noting it works reliably even when off-screen or obscured.

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 when to use (buttons, menu items, hyperlinks) and why (works reliably off-screen). Also provides a prerequisite (if app stopped at breakpoint, resume first) and fallback behavior (falls back to Click() if InvokePattern not supported).

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