bg3_se_reset_lua

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: it re-runs Bootstrap scripts and is scoped to mods loaded at game start. But it omits the practical consequences of a reset (e.g., loss of runtime Lua state, whether it is disruptive or reversible) that an agent would want before invoking it.

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 that names the operation, its mechanism, and its scope limitation without a wasted word.

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 no explanation, and with zero parameters the remaining burden is behavioral. It covers the mechanism and scope well but leaves the action's side effects and its routing relative to sibling reload tools unstated.

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 tool takes zero parameters, so there are no parameter semantics to explain; the baseline for a zero-parameter tool is 4.

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 specific verb and resource: 'Reload Script Extender Lua', clarifying that it 're-runs every loaded mod's Bootstrap scripts from its pak/loose files'. This is more precise than a generic 'reset', though it doesn't explicitly distinguish itself from potentially similar siblings like bg3_se_hot_load or bg3_refresh.

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 console-`reset` framing and the constraint 'Only affects mods that were loaded at game start' imply when this applies, and hint that newer/hot-loaded mods may be outside its scope. However, it never explicitly states when to use this versus alternatives such as bg3_se_hot_load, so usage is left to inference.

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