Remember session settings

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

With no annotations provided, the description carries the behavioral burden. It discloses persistence (in-memory only), auto-remember behavior, clearing via empty string, the outputDir default, and the requirement that umodelExe and gamePath must come from the user. This is far beyond what the schema shows.

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 dense but every clause adds value: main purpose, auto-remember note, user-confirmation requirement, fallback guidance, clearing semantics, and default. It is structured with clear signposts ('NOTE', 'IMPORTANT') and no filler.

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?

For a 7-parameter state-mutation tool with no annotations and no output schema, the description covers all necessary decisions: when to invoke, how to clear, defaults, user-confirmation, and alternatives. It leaves little room for mis-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?

Though schema coverage is 100%, the description adds operational meaning: it groups parameters by whether they are auto-remembered or need explicit setting, explains that empty strings clear values, and documents the Downloads default for outputDir. This helps the agent decide what to pass.

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 opens with 'Store settings in the in-memory session' and clarifies nothing is written to disk, giving a specific verb and resource. It also distinguishes this tool from auto-remembered values and sibling tools like umodel_find_exe, making its scope unambiguous.

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?

It explicitly states 'use it only to set values ahead of time, clear them (empty string), or configure pure settings' and identifies when not to use it ('most values are auto-remembered'). It also names the alternative fallback, umodel_find_exe, with a clear condition for using it.

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