render-set_settings

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

No annotations are provided, so the description carries the full burden. It only says 'Set common render settings', which merely indicates mutation without addressing side effects, scope (current scene? global?), persistence, or whether settings are applied to subsequent renders. There is no consideration of auth, permissions, or reversibility.

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?

One short, front-loaded sentence is highly concise and free of filler. However, it is more under-specification than deliberate condensation; the sentence offers little nuance but earns its place as a minimal label.

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 tool with six optional parameters and no output schema or annotations, the description is insufficiently complete. It does not mention what these settings affect, how they relate to rendering workflows, or when they take effect. A sentence about the target workflow (e.g., 'Sets parameters for render-still') would improve completeness.

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?

The description adds no parameter-level information, and schema description coverage is 0%. While the schema properties have descriptive titles and enums, the description does not compensate for the low coverage or clarify interactions between parameters (e.g., how transparent relates to image_format). This is less than ideal.

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 verb 'Set' and the resource 'render settings', which accurately reflects the tool's function. However, the qualifier 'common' is vague, and it does not distinguish itself from sibling tools like render-settings or render-still, though the set action is implied.

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 provides no guidance on when to use this tool versus alternatives such as render-still or render-settings. It neither states prerequisites, exclusions, or the intended context (e.g., before rendering a still image). This is a clear gap for an otherwise flexible settings setter.

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