ui_get_selected_item

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

Annotations already indicate read-only and idempotent behavior. The description adds a critical backend-specific limitation ('FlaUI backend returns selection for the first item only'), which is valuable beyond annotations. However, it does not specify behavior when no item is selected or error conditions.

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 concise (5 sentences plus argument list) and front-loaded with the primary purpose. Every sentence adds value without redundancy. The arguments are clearly listed with inline definitions.

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 simplicity (3 params, no output schema), the description covers the core functionality and parameter semantics. It mentions what is returned (name, index, properties) but omits details on handling empty selections or errors, which would be helpful for a complete understanding.

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 description adds meaning to all three parameters: automation_id is the AutomationId of a list/grid/combobox control; root_id scopes the search; xpath is an optional XPath expression available only in FlaUI backend. Since the input schema has 0% description coverage, the description fully compensates.

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 verb 'Get' and the resource 'currently selected item in a list/grid control'. It distinguishes from sibling tools like ui_find_element by explicitly noting that it returns only the first item in multi-selection, whereas ui_find_element can inspect individual items for full state.

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 provides explicit guidance on when to use ('useful for verifying selection state after clicks or keyboard navigation') and when not to use ('Use ui_find_element to inspect individual items for full multi-selection state'). This directly addresses alternatives.

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