renforge_stop

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

No annotations are provided, so the description must disclose behavioral traits itself. It mentions 'clean up' as a side effect, but does not explain what cleanup involves, whether the action is destructive, whether it affects saves, or what happens if no game is running. This omits critical details for a stopping 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 sentence, concise, and front-loaded with the primary action. Every word contributes to the core message without extraneous detail.

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?

While the tool is simple (one parameter, no nested objects), the description lacks essential context: it does not explain the project_path parameter, the cleanup process, or any preconditions. The presence of an output schema is noted but not described, and the description is insufficient for safe invocation.

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 schema has one parameter, project_path, with 0% description coverage. The description does not mention or explain this parameter at all, leaving the user to guess what path is expected (project directory vs. game executable). This is a significant gap.

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 the tool's action: 'Stop a running game or cancel its in-progress launch, then clean up.' This uses specific verbs ('stop', 'cancel') and identifies the resource ('game'/'launch'), distinguishing it from siblings like renforge_launch and renforge_launch_status.

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 when to use the tool (when a game is running or a launch is in progress), but it does not explicitly mention alternatives or circumstances to avoid. It does not reference related tools like renforge_launch_status or renforge_advance.

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