ui_grid

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

Annotations only include openWorldHint=false, which is not explained or expanded upon. The description does not disclose side effects, permissions, or whether operations are read-only or destructive beyond implying multiple modes (read/select/assert).

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?

A single sentence with no fluff, but it may be too terse given the tool's complexity. While concise, it sacrifices necessary detail.

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 20 parameters, no output schema, and high complexity, the description is severely incomplete. It does not explain actions, row identifiers, or behavior, leaving the agent unable to use the tool effectively.

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?

With 20 parameters and 0% schema description coverage, the description fails to explain any parameter's meaning or relation to the actions. The agent receives no assistance on how to populate action, row_index, columns, or other critical fields.

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-action ('Read, select, or assert') and the resource ('WPF DataGrid row evidence'), distinguishing it from sibling UI tools which handle generic clicks, selections, or property reads.

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?

No guidance is provided on when to use this tool versus alternatives like ui_find_element, ui_select_items, or other grid-specific tools. The description does not mention exclusions or context.

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