configure_post_processing

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the mutation/overwrite profile is partly covered by structured data. The description adds useful context by enumerating the effects it governs (bloom, motion blur, DOF, AO, GI), but it never says what existing configuration is replaced or whether it applies globally versus to a volume, which is the key behavioral question for a destructive preset switch.

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 opening sentence is tight and front-loaded, but it is followed by a raw dump of roughly 29 return field names with no grouping or explanation. That block is padding rather than conciseness, since a structured output schema or a summarized return description would communicate the same thing far more efficiently.

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?

With no output schema, the description does at least attempt to disclose the return surface, which is legitimate. However it omits operationally important context (scope: global vs. volume; required world/level state; whether it requires an open editor world), so for a destructive write tool it is only minimally complete.

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 100%, so the single parameter is already documented. The description repeats the same five preset values rather than adding new semantics (e.g. what 'Medium' actually changes versus 'Low'), so it does not exceed the baseline.

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?

States a specific verb and resource ('Configure post-processing settings') and scopes it to preset levels ('Enabled', 'Disabled', 'High', 'Medium', 'Low') that map onto named effects. It does not, however, distinguish itself from the very similar sibling set_post_process_setting, nor does it say whether it targets global settings or a post-process volume.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as set_post_process_setting, set_post_process_color_grading, or set_post_process_volume_settings. The agent must infer the tool's role purely from the name.

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