get_post_process_settings

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

Annotations already establish readOnly/idempotent/non-destructive, so the description's job is lighter. It adds genuinely useful context by explaining that every value carries its bOverride_* flag so the caller can see what is actually active — behavior not captured by any annotation.

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 purpose is front-loaded in the first sentence and the return block earns its space since no output schema exists. The opening sentence is slightly convoluted, but overall it is appropriately sized for the amount of return-shape information conveyed.

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 takes on the burden of documenting the return value and does so thoroughly, enumerating color_grading, white_balance, scalars, and the two method ints. Complete for an agent to interpret the response, though it omits the meaning of the exposure_method/gi_method integer values.

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?

Only one parameter with 100% schema description coverage, so the schema already documents actor_name. The description repeats actor_name in the return shape but adds no syntax or format detail beyond the schema, making the baseline 3 appropriate.

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 ("Read") and resource (a PostProcessVolume's color grading and scalar settings), and ties itself to the sibling set_post_process_setting as its counterpart. It does not, however, differentiate itself from the near-identical getter get_post_process_volume_settings, which is a real ambiguity for an agent.

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 reader that was missing" and the pairing with set_post_process_setting imply when to use it, but there is no explicit when-to-use or when-not guidance against the many other post-process getters in the sibling list. Usage is implied rather than stated.

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