render_set_cameras

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

Annotations already declare a non-destructive, non-open-world mutation, so the safety profile is covered. The description adds nothing beyond purpose: it never says whether the enable/disable lists are additive or replacing, whether disable wins over enable, whether both-null resets to defaults, or whether the setting persists in the scene file vs. only for the session.

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?

A single front-loaded sentence with zero filler, correctly naming the downstream tools. It is efficient, though its terseness is part of why the behavioral and parameter gaps exist.

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?

An output schema exists so return values need no explanation, but for a two-parameter configuration mutation with 0% schema description coverage the description does too little: an agent cannot tell what values to pass or what the enable/disable semantics are.

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% and the two parameters (enable, disable) are opaque anyOf arrays of integer-or-string with no titles beyond the key names. The description gestures at 'which cameras' but never says the values are camera names/indices, nor how the two lists interact, so it does not compensate for the coverage 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?

States a concrete verb+resource: choosing which cameras get rendered, scoped explicitly to the render_images and render_videos tools. That tells an agent the tool is a configuration step in front of those two render calls, though it never distinguishes itself from near siblings like camera_set_active or render_set.

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 phrase 'render on render_images and render_videos' implies the tool is used to configure cameras before invoking those renders, but there is no explicit when-to-use statement, no prerequisites, and no mention of alternatives such as camera_set_active. Usage must be inferred.

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