validate_scene

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

With no annotations, the description must carry the full burden of behavioral disclosure. It communicates that this is a preflight check rather than a final render, but it does not explain whether a test render is actually produced, whether the operation is read-only, what side effects may occur, or what the response looks like. The render-related parameters suggest possibly more than a pure schema check, but that is left ambiguous.

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 concise and front-loaded, with no wasted words. However, it is too sparse for a tool with 9 parameters and no annotations; the absence of necessary supporting context makes it under-sized rather than ideally concise.

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 description captures the tool's core purpose but is incomplete for a complex invocation. It gives no sense of what a successful validation looks like, what the returned data contains, how the render-related parameters affect validation, or what 'preflight' actually evaluates. Given no output schema and no annotations, this leaves meaningful gaps for an agent.

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 description provides no parameter guidance. With 9 parameters including aov, backend, checkpoint_interval_seconds, samples, and denoise, an agent cannot infer the semantics of these fields from the description alone. The description does nothing to compensate for the schema's lack of documentation.

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 uses a specific verb ('Preflight') and names the exact resource ('USD or RDL scene'). It also clearly positions the tool as a pre-render validation step, making it easy to distinguish from siblings like start_render or launch_interactive_viewer.

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?

'Before committing to a render' gives a clear context of when to use this tool. It does not explicitly name alternatives or exclusions, but the timing guidance is strong enough to route the agent toward validation before rendering.

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