add_to_selection

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

With no annotations provided, the description carries the full burden for behavioral transparency. It clearly discloses that the tool uses the 'UIA SelectionItem pattern' and explicitly states the key non-destructive behavior: it 'does not deselect existing items'. This provides essential behavioral context beyond the parameter schema.

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 that efficiently conveys the action, target, mechanism, and critical behavioral note. Every part earns its place with zero 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 is simple (1 parameter, no output schema, no nested objects), the description adequately covers the purpose, mechanism, and key behavior. It does not explain return values, but with no output schema defined, some users might expect guidance on what the tool returns (e.g., success/failure). However, the tool's simplicity makes this a minor gap.

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 does not add any meaning beyond the input schema for the single parameter 'elementId'. Since the schema description coverage is 100% and the schema already states 'Element ID returned by find_element', the description provides no additional parameter semantics. Baseline score of 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 'Add', the resource 'item to the current selection in a multi-select container', and explicitly distinguishes from a deselect behavior by noting 'does not deselect existing items'. This provides a specific and unambiguous purpose.

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 implies usage when you need to add an item to a multi-select selection without clearing existing selections, but it provides no guidance on when not to use this tool (e.g., for single-select containers or when you need to replace the selection) or any alternatives among the many sibling tools like 'select_item' or 'remove_from_selection'.

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