render_preview

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

With no annotations, the description carries the full behavioral burden. It discloses only that a status and path come back; it says nothing about whether rendering is synchronous or long-running, whether it blocks, whether it can be cancelled, or what the default `rerender=true` implies about re-computing an existing mix. For a render operation these are material gaps.

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?

A single front-loaded sentence with zero filler; the verb and outcome lead. It is efficient, though arguably terse to the point of under-specification given the 0% schema coverage.

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?

An output schema exists, so return values need not be explained — that is the one thing covered. But for a render tool with two undocumented parameters and no annotations, the description omits nearly everything an agent needs to invoke it confidently.

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%, so the description must compensate and it does not. Neither `rerender` (default true) nor `project_path` (nullable) is mentioned or explained, leaving the agent to guess what rerendering does and whether an omitted project path uses a session default.

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?

Names a specific verb and resource: 'Render a preview mix'. That is clear, but it does not distinguish itself from the many sibling render/export tools (render_final, render_status_tool, export_audio_tool, bounce_audio_tool). A reader cannot tell from the description alone when a 'preview' render is the right call versus a final render.

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 when-to-use guidance, no mention of when-not-to-use, and no reference to the closest alternatives (render_final, render_status_tool). The word 'preview' hints at intent, but the agent must infer the entire selection logic.

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