preset_apply

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

No behavioral disclosure is provided beyond the title. The description does not mention that applying a preset modifies the scene/object, what settings are overwritten, whether the operation is reversible, or any side effects. With no readOnly/destructive annotations, the description carries this burden and fails to address 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?

The description is extremely concise and lists the key parameter values without wasted words. However, it is so sparse that it omits the action and effect, making it efficient but not fully informative.

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 mutation-style tool with no annotations and no output schema, the description should state what applying a preset does to the target. It covers the parameter values but leaves the actual behavior and invocation context mostly to inference from the tool name.

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 schema provides only a string parameter with a default, and schema description coverage is 0%. The description compensates by enumerating the valid preset values: studio_lighting, turntable, and character_base, which is essential for calling the tool correctly.

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 identifies the resource (presets) and enumerates the available options, and the tool name plus annotation title 'Apply Preset' make the action clear. It does not explicitly state the verb in the description itself, and it does not differentiate from preset_list or preset_create_from_scene in the text.

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?

There is no guidance about when to use this tool versus sibling tools like preset_list, preset_create_from_scene, or preset_get_hint. The description only lists preset names, leaving the selection context entirely implicit.

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