select_item

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

With no annotations provided, the description carries the full burden. It discloses the underlying automation pattern (UIA SelectionItem) and the target controls (list box, tab control, combo box), but does not specify any side effects, required permissions, or failure modes (e.g., what happens if elementId is invalid or the item is already selected). This is adequate but not comprehensive.

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 that are front-loaded with action and purpose, every clause adds value. The technical detail about the UIA pattern is included without verbosity.

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 (1 required param, no output schema, no nested objects, 100% schema coverage), the description is complete enough. It covers what the tool does and when to use it. A small gap is not explaining the return value or confirming successful selection, but the lack of output schema lowers expectations.

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 input schema has 100% coverage with elementId already described as 'Element ID returned by find_element'. The description adds no additional meaning beyond confirming the control types, which is already reasonable from the tool name and schema. Baseline 3 is appropriate.

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 'select', the resource 'item in a list box, tab control, or combo box', and the specific automation pattern (UIA SelectionItem). It also explains that this is the preferred method over click when click does not trigger selection, distinguishing it from similar tools like click_element.

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 explicitly advises to use this tool when 'click does not trigger selection', providing a clear when-to-use context. However, it does not mention any when-not-to-use scenarios or alternative tools like invoke_element for non-selection actions, which would have made it a 5.

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