ui_realize_virtualized_item

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

Beyond the idempotentHint annotation, the description details the operation's effect (forces into visual tree), idempotency, error cases (item not found, container not virtualizing), and the exact return object structure. No contradictions with annotations.

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 well-structured: purpose first, then background, then idempotency, return values, and parameters. All sentences are necessary and informative. 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?

The description covers the virtualization concept, multiple return cases, and error conditions. Lacks a concrete example or guidance on obtaining the container_automation_id, but overall is sufficient for the tool's complexity. Minor gaps.

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?

Schema description coverage is 0%, so the description must compensate. It lists the three parameters and specifies supported values for prop_name (AutomationId, Name, ClassName). This adds value but could provide more detail or examples. Baseline 3 is appropriate given partial compensation.

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 tool's purpose: realizing a virtualized list/grid item. It explains the context of virtualized lists and that this tool forces an item into the visual tree, distinguishing it from sibling UI tools that operate on already-realized elements.

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 explains when to use this tool: before ui_click or ui_find_element on virtualized lists. It mentions idempotency and safe re-realization. While it doesn't explicitly list when not to use it or alternatives, the context is clear and implicit.

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