configure_render_output

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

Annotations already declare the mutation/safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true). Beyond that, the description explains what is actually touched: it finds-or-adds a UMoviePipelineOutputSetting to set resolution/output dir and adds the matching image-sequence output container, plus notes the exr fallback. This adds meaningful behavioral context, though it doesn't spell out the destructive aspect of overwriting existing config.

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?

Front-loaded with the purpose, followed by the mechanism and a clear Returns block. Every sentence is informative, though the mechanism sentence is dense. Overall well-structured and appropriately sized.

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 helpfully includes the return shape (configured, settings, etc.), and all parameters are documented via the schema. For a mid-complexity config-mutation tool, this is nearly complete, missing only explicit usage ordering.

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 schema already documents format, job_name, output_dir, resolution_x, and resolution_y including the pairing constraint. The description adds little beyond the schema, so the baseline of 3 applies.

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 (Configures) and resource (output resolution/directory/image format on a render job's config), and further disambiguates the mechanism (UMoviePipelineOutputSetting on the primary configuration). This clearly distinguishes it from siblings like create_render_job, cancel_render_job, and render_sequence_to_movie.

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 implies usage on an existing render job's config and the schema notes job_name comes from create_render_job, so the context is implied. However, there is no explicit when-to-use vs alternative, and no statement of prerequisites or ordering relative to create_render_job or render_sequence_to_movie.

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