renforge_list_ui_elements

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

No annotations are provided, leaving the description responsible for conveying side effects and behavioral context. The description introduces the term 'frame guard' without explanation and does not clarify whether the operation is read-only, requires a running game, or has other side effects. This is a significant gap for an automation tool.

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, well-structured sentence that front-loads the core action and resource. It contains no filler and communicates the essential purpose efficiently.

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 having an output schema, the tool has 4 parameters, 0% schema description coverage, and no annotations. The description fails to explain key parameters or usage context, making it insufficient for an agent to invoke correctly without additional guesswork. The 'frame guard' phrase adds ambiguity rather than clarity.

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 mentions none of the parameters (text, screen, element_type, project_path). The description adds no meaning beyond the schema, leaving the agent to guess parameter semantics. This is a critical shortfall.

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 states a specific action ('List'), a clear resource ('visible focusable Ren'Py controls'), and additional details ('with bounds and frame guard'). This clearly distinguishes it from sibling tools like renforge_get_ui_element_bounds or renforge_list_choices.

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 for inspecting UI elements but does not explicitly state when to use this tool over alternatives or mention any exclusions. Sibling tools exist for related but distinct purposes, yet no comparison or 'use this instead' guidance is provided.

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