render_project

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

No annotations are provided, so the description carries the full behavioral burden. It notes the LAME requirement for mp3, which is useful, but omits whether an existing file is overwritten, whether this is a long blocking operation, whether it mutates project state, and what it returns. For a write-to-disk tool with zero annotation coverage these are significant 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?

The purpose sentence comes first and the parameter notes are terse, information-dense bullets with no filler. It is slightly under-structured only in that the parameter lines aren't clearly marked as parameter documentation.

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?

Good parameter coverage, but for a rendering/mutation tool with no annotations and no output schema, the description says nothing about overwrite behavior, the returned result, failure modes, or the relationship to the sibling render tools. It is adequate but noticeably incomplete.

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 largely does: it gives valid values for format (with the LAME caveat), example rates for sample_rate, allowed depths for bit_depth including the 'WAV only' constraint, and channel meanings. Only output_path is unexplained, and its name and required status make it self-evident.

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?

States a specific verb and resource ('Render the entire project to a file'), which is unambiguous. However, it never distinguishes itself from the closely related siblings render_time_selection, render_stems, and render_regions, leaving the agent to infer the scope difference.

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?

No guidance on when to use this versus the other three render tools in the sibling list. There are no prerequisites, no exclusions, and no mention of what happens if the project is unsaved or the transport is running.

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