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

Annotations already indicate the tool is not read-only (readOnlyHint=false) and not destructive, and the description adds the key behavioral context that actual MP4 export happens client-side in the user's browser, so no server render cost is incurred. This is a meaningful trait an agent needs to know when choosing between save and render.

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?

Three purposeful sentences: the first states the core function and return, the second explains workflow context, and the third routes to the alternative. No repeated or filler content; every sentence earns its place.

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?

With no output schema, the description still discloses the important return value (`openUrl`) and its downstream effect (video drops into the Studio for client-side export). It also covers the primary input (`doc`), the optional name, and how to choose between this and `neuron_studio_render`, making the tool safely invocable.

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 coverage is 100%: `doc` and `name` each have descriptions, including the default for `name`. The description does not add parameter-level detail beyond restating the `doc` concept, so the high schema coverage is sufficient and the baseline of 3 applies.

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 names a specific action ('Persist a ProjectDoc') and a concrete return value (`openUrl`), and the title states the resource (video save + open link). It also distinguishes itself from `neuron_studio_render`, which is a sibling that performs server-side rendering.

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?

It explicitly says when to use this tool: after building with `neuron_studio_apply`/`agent`, when handing the user a link in the hybrid flow. It also names the alternative `neuron_studio_render` and excludes it for all but headless/unattended server renders.

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