set_post_process_setting

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

Annotations already declare readOnly=false, destructive=true, and idempotent=true, so the safety profile is covered. The description still adds useful behavioral context by explaining that it sets the bOverride flag plus the field and 'reads back', and it documents the returned applied/applied_value pair. It does not explain what the destructive hint means (e.g. overwriting an existing override).

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 core verb is front-loaded, but the body is a dense run-on listing of settings with irregular spacing and no clear structure, mixing setting names, enum meanings, and return shape in one block. It is informative but not crisp.

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 3-param mutation tool the definition covers the mechanism (bOverride + readback), lists domain values, and inlines the return object, which compensates for the absent output schema. The main missing piece is why the operation is flagged destructive and how it relates to sibling post-process tools.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it enumerates several valid setting names and gives the enum index mappings for exposure_method (0=Histogram,1=Basic,2=Manual) and lumen_gi (0=None,1=Lumen,2=ScreenSpace,3=Plugin).

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 states a specific verb+resource+scope: sets a setting on a PostProcessVolume and explains the bOverride-flag mechanism. It is understandable in isolation, but it does not differentiate itself from very close siblings such as set_post_process_volume_settings, configure_post_processing, or set_camera_post_process.

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?

Usage is only implied by the nature of the tool ('set a setting'). There is no explicit guidance on when to choose this over set_post_process_volume_settings or set_post_process_color_grading, and no prerequisites or exclusions are named.

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