uds_apply_preset

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

With no annotations, the description carries the burden. It usefully discloses mutation, map-saving, the in-game override, and the editor-open refusal unless allowWithEditorOpen. However, it omits the dryRun flag (default true), which could affect whether the map is actually saved, so the disclosure is incomplete.

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?

Three sentences, front-loaded with the core action and side effect, followed by the two most decision-relevant caveats. 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 mutating, six-parameter tool with no annotations and no output schema, this is not complete. The critical in-editor caveat and mutation guard are present, but the unqualified statement that it saves the map conflicts with a dryRun default of true, and the return value and timeout behavior are unexplained.

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?

Schema description coverage is 0%, so the description must illuminate the six parameters. It explains the preset concept, the target as sky actor (actorLabel), and the allowWithEditorOpen guard, but leaves map, dryRun, and timeoutSeconds without any semantic guidance in either schema or description.

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 a specific verb ('Apply'), a concrete resource ('sky actor'), a named preset concept, and a side effect ('save the map'). It distinguishes this from sibling tools by scoping it to editor-time UDS lookdev checks, which none of the sibling names suggest.

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 says this is for in-editor look checks only and warns that runtime phase profiles override the preset every tick in-game, giving a clear when-not-to-use condition. It stops short of naming an alternative sibling, so it earns 4 rather than 5.

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