renforge_advance

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

No annotations are provided, and the description does not disclose any behavioral traits such as whether the tool blocks, modifies game state, requires specific conditions (e.g., active dialogue), or what happens if no dialogue exists. This leaves significant uncertainty for the agent.

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 sentence with no wasted words, which is structurally concise. However, it is under-specified to the point of being vague, so the brevity is not an asset here. The structure does not add clarity.

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?

With an output schema present but not described, and a sparse input schema, the description is insufficient. It does not explain return values, side effects, or the broader interaction flow, leaving the context incomplete for an agent to invoke it correctly.

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 input schema has one parameter (project_path) with no description, and schema description coverage is 0%. The tool description does not mention the parameter at all, so the agent receives no semantic guidance about what project_path should contain (e.g., path format, scope).

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 verb ('Advance') and resource ('current dialogue'), making the core action clear. It distinguishes somewhat from siblings like select_choice (which selects options) and send_input (which sends arbitrary input), but lacks detail on what 'advance' entails (e.g., next line, confirm, skip).

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. There are no exclusions, prerequisites, or mentions of related tools, leaving the agent without context for choosing this over select_choice or control.

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