geck_list_view_rows

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. 'Read' implies a non-mutating operation, but it does not explain how the target window is resolved, how the handle may be omitted, whether this is safe to call on any ListView, or how errors are surfaced.

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 front-loaded sentence with a clear verb and object. It contains no filler or redundant phrases, making it as concise as possible.

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?

Despite the presence of an output schema, the tool has seven undocumented parameters, no annotations, and no usage context. The description leaves an agent without enough information to know when to call it, how to choose parameters, or what relationship this tool has to the rest of the GECK workflow.

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%, and the description adds nothing about any of the seven parameters. An agent receives no meaning for handle, list_index, max_rows, title_regex, backend, start_row, or max_columns beyond their bare names and defaults.

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 names a specific verb ('Read') and a precise resource ('rows from a Win32 ListView in a GECK window or dialog'), so an agent can tell what the tool acts on. However, it does not explicitly distinguish itself from sibling tools like geck_find_list_rows, which likely performs a related row-reading operation.

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?

There is no guidance on when to use this tool, what prerequisites are needed (e.g., a valid window handle), or when to prefer an alternative such as geck_find_list_rows or geck_control_tree. The description only states the action itself.

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