renforge_list_choices

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

With no annotations, the description carries the burden of disclosing behavior. It implies a read-only operation ('List') and describes the output, but does not explicitly state that it does not modify state, whether it requires a running game, or what happens when no menu is present. This is adequate for a simple listing tool but leaves some behavioral ambiguity.

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 no wasted words. Every part adds value, and it is immediately clear what the tool does and what it returns.

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 description lacks crucial context: the meaning of project_path, when to use this over sibling tools, and any error/edge-case behavior. For a simple tool with one parameter and 0% schema coverage, the description is incomplete.

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?

The only parameter, project_path, has no schema description and is not mentioned in the tool description. The name suggests it is a path to a Ren'Py project, but this is not explicit. With 0% schema coverage, the description should clarify the parameter's role, and it fails to do so.

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 a specific action ('List') and a specific resource ('on-screen menu choices'), and specifies the output content ('text + index'). It differentiates from siblings like renforge_select_choice (which selects) and renforge_list_ui_elements (which lists UI elements generally). This is a concise and unambiguous purpose.

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. It does not mention that it is a precursor to renforge_select_choice, nor does it clarify when on-screen menu choices are available. The description leaves usage context entirely implied.

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