start-render

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

No annotations provided, so the description carries full burden. It discloses that the tool blocks After Effects until render finishes, making the UI unresponsive, and that render continues after timeout. This is critical behavioral context beyond basic rendering. Could mention prerequisites like AE must be running, but still strong.

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?

Two sentences plus a brief warning, no fluff. Front-loaded with purpose, then critical behavioral info. Every sentence is substantive and 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?

Given no output schema, the description covers purpose, usage prerequisite, blocking behavior, and timeout handling. It could mention return value or success confirmation, but overall it is complete for a tool with one parameter. Complexity is moderate, and the description addresses the main concerns.

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?

The only parameter, timeoutMs, is fully described in the schema (100% coverage). The description adds minor value: 'Set higher for long renders' and the default (300000 ms). Baseline 3 is appropriate since schema already provides meaning.

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 clearly states 'Render all QUEUED items in the After Effects render queue,' specifying the verb (render) and resource (queued items). It distinguishes from sibling tools like 'render-aerender' and 'render-queue' by mentioning the prerequisite 'Add items first with add-to-render-queue.'

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 explicit context: items must be queued first using add-to-render-queue, warns about blocking AE UI, and advises raising timeoutMs for long renders. It also notes that after timeout, the render continues and status can be checked later with render-queue. No explicit 'when not to use' but sufficient guidance.

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