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

Annotations are all false, so the description carries the behavioral burden. It clearly discloses the asynchronous nature — returns a job id and requires polling neuron_studio_render_status until completed — plus the media URL precondition and plan requirement. It does not cover failure modes or final output access, but it adds substantial behavioral context beyond the annotations.

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 three tight sentences with no filler. It front-loads the core action, then gives the async contract and prerequisites, and every sentence contributes necessary information.

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?

Given the async nature, nested input object, and lack of an output schema, the description covers what to submit, how the job is tracked, and the critical media/plan preconditions. It does not explain where the rendered MP4 ends up or enumerate error cases, but it is complete enough for correct 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 100%, so the schema already documents the required doc object and optional sceneId. The description adds the practical constraint that embedded media must be server-reachable URLs, but does not add per-parameter syntax or formatting details beyond what the schema provides.

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 states a specific verb and resource: submit a Studio ProjectDoc for a headless MP4 render. It also clarifies the output type and names the corresponding status-polling tool, which distinguishes it from other studio video tools like generate_video or transform_video.

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 gives clear workflow guidance: media in the document must be server-reachable URLs, and import/upload media tools should be used first. It also notes the Pro+ plan requirement. It does not explicitly contrast this tool with neuron_studio_generate_video or other alternatives, but the render-specific wording supplies enough context.

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