set_render_settings

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

No annotations exist, so the description carries the full burden. It does not say whether these settings are session-scoped or saved into the scene file, what happens with an unsupported renderer string like 'vray', whether omitted params are left untouched, or that this mutates the scene document. Only the renderer-value examples add real information.

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?

Two short sentences that are front-loaded with the core purpose. The parenthetical is slightly cryptic in placement but does not add significant bloat.

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?

A five-parameter scene-mutating tool with zero schema descriptions and no annotations leaves the agent guessing about units, optionality semantics, persistence, and validation behavior. An output schema exists, so return values need not be covered, but the input-side and behavioral gaps are substantial.

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 0%, so the description must compensate and largely does not. It gives example values for 'renderer' but says nothing about width/height (presumably pixels), start_frame/end_frame (frame range, float type), or the fact that all five parameters are optional with null defaults.

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+resource ('Configure Maya render settings') that is clearly distinct from read-only siblings like get_scene_info. The renderer examples clarify the domain, though it stops short of differentiating from neighbors such as render_scene or export_scene.

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 parenthetical about render_scene supporting only 'arnold' and 'mayaSoftware' hints that this tool is the place to set a renderer before rendering, implying an order of operations. However there is no explicit when-to-use statement, no prerequisites, and no guidance on which sibling to prefer for related tasks.

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