set_render_settings

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

There are no annotations, so the description carries the burden of behavioral disclosure. It mentions 'persistent' and contrasts with render_preview's temporary override, which is helpful. However, it doesn't disclose side effects (e.g., whether the change is applied immediately, whether it requires saving the scene, or if it affects all future renders). More transparency would be expected for a mutation tool with no annotations.

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—two sentences—and well-structured. It front-loads the purpose and then provides usage guidance, with zero fluff. Every sentence earns its place, making it efficient for an agent to parse.

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?

The tool has 10 parameters, all optional, no output schema, and no annotations. The description gives almost no context beyond the persistent-vs-temporary distinction. It doesn't explain what the settings affect, typical use cases, or relationships to other tools like get_render_settings. For such a parameter-heavy tool, this is insufficient.

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 only 40% (4 of 10 parameters have descriptions). The description adds no parameter-specific meaning—it only references 'resolution, samples and format' in the context of render_preview, not for this tool. Since coverage is low, the description should compensate by explaining parameters, but it doesn't, so this is a significant gap.

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 clearly states the tool's purpose: changing the scene's persistent render settings. It uses a specific verb 'change' and a clear resource 'scene's persistent render settings', and explicitly contrasts with the sibling tool render_preview, which makes the distinction obvious.

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 gives explicit usage guidance: it explains that render_preview overrides and restores settings, and that this tool should only be used when a persistent change is desired. It names the alternative (render_preview) and the condition, leaving no ambiguity about when to choose this tool.

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