start_render

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

With no annotations, the description carries the full burden of disclosing behavior. It usefully reveals that the render is asynchronous and returns immediately with a job ID, but it does not mention that a background job is created, that the operation can fail after returning, or how the job can be tracked or cancelled. Partial transparency only.

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 single sentence is front-loaded with the core action and return behavior, with no wasted words. It is efficient, though slightly too sparse to be maximally helpful.

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?

This is a 10-parameter tool with no annotations, no output schema, and zero schema description coverage, yet the description only covers the start/return contract. It omits all optional parameter semantics and any guidance on how to monitor or manage the returned job, leaving the agent under-informed for a real invocation.

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 mentions no parameters at all. With 10 parameters (including scene as required and options like samples, camera, backend, and checkpoint_interval_seconds), the agent receives no semantic help beyond parameter names and types, so the description fails to compensate for the schema 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 uses a specific verb ('Start') and a specific resource ('asynchronous MoonRay render') and clearly states the return value (job ID). This distinguishes it from sibling render-control tools like render_status or cancel_render, as well as interactive-viewer tools like 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?

There is no guidance on when to choose this tool over alternatives such as launch_interactive_viewer or render_preview, and no exclusions or conditions are stated. The word 'asynchronous' hints at batch use, but the agent is left to infer the selection criteria.

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