ue_apply_mood_preset

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

The description clarifies that the tool applies changes to multiple visual elements (consistent with non-read-only behavior) and implies idempotency by saying 'apply' without side effects. Annotations idempotentHint=true and destructiveHint=false are supported, and the description adds context of what gets modified.

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 sentences, no wasted words. The first sentence states the action and scope; the second provides guidance. Information is front-loaded and clear.

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?

Given a single required parameter and existence of an output schema (not shown but noted), the description covers the core purpose, parameter sourcing, and affected systems. It does not describe return values or error cases, but those may be covered by the output schema. Complete enough for the complexity.

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?

With 0% schema description coverage, the description compensates by telling the agent to call ue_list_mood_presets for valid names, but does not elaborate on parameter format or constraints beyond the schema type. Baseline for low coverage is 3, and this description provides adequate but not rich semantics.

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 applies a named cinematic mood as a coordinated package, specifying affected elements (sun angle/colour, fog, clouds, post-process colour grade). This distinguishes it from sibling tools like ue_set_time_of_day or ue_setup_sky_atmosphere.

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 instructs to call ue_list_mood_presets for available names and provides example names (golden_hour, noir, etc.), giving clear context on how to select parameters. It does not explicitly state when not to use it but implies a workflow.

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