Renforge List Ui Elements

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

With no annotations, the description carries the full burden, and it does disclose filtering behavior (only visible, focusable controls) and return content (bounds). However, 'frame guard' is unexplained jargon, and it never says whether this is a read-only operation or whether a running game/session is required.

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 front-loaded sentence with no wasted words, leading with the verb and resource. The terse phrasing slightly hurts comprehension because 'frame guard' is never defined.

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?

An output schema exists so return values need not be explained, but four parameters with 0% schema coverage and no annotations leave the filtering semantics and prerequisites (e.g. whether the project must be running) undocumented. The description is too thin for a tool with this much structured-data silence.

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 schema documents nothing about text, screen, element_type, or project_path, and the description offers no compensating explanation of their meaning or format. The phrase 'visible focusable' only loosely hints at the element_type filter.

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?

States a concrete verb ('List') and resource ('Ren'Py controls') with a scope qualifier ('visible focusable') and names what is returned ('bounds and frame guard'). This separates it from siblings like renforge_click_element or renforge_scene_tree, though it never names an alternative directly.

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 explicit when-to-use or when-not-to-use guidance and no mention of the sibling tools (renforge_scene_tree, renforge_get_ui_element_bounds, renforge_click_element) that overlap in purpose. Usage is only implied by 'visible focusable'.

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