bg3_se_hot_clean

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

No annotations provided, so the description carries the full burden. It usefully discloses that 'Entries already hot-loaded stay in the running session until restart' — a non-obvious behavioral trait. It does not cover safety/reversibility or required game state, but the session-persistence detail is valuable.

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?

Two tight sentences, no waste. The scope (path pattern) is front-loaded and the behavioral caveat follows.

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?

Output schema exists so return values needn't be explained. For a zero-param cleanup tool, the description covers what it removes and the session-persistence caveat. Missing: whether the operation is safe/idempotent and any precondition (e.g., game closed).

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?

Zero parameters, so baseline is 4. The description correctly implies no arguments are needed beyond the fixed path pattern it targets.

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?

Specific verb+resource: 'Remove the loose hot-load folders (Data/Public/BG3DataHot_*) from the game install.' Names the exact path pattern being cleaned. Distinguishable from siblings like bg3_se_hot_load and bg3_test_cleanup by the specific target.

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?

Implied context — this is a cleanup tool, use it to remove hot-load folders. But no explicit when-to-use or when-not, and no reference to alternatives like bg3_se_reset_lua. The sibling name bg3_se_hot_load suggests a pair, but the description doesn't state the relationship.

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