render_project

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

destructiveHint: true is consistent with the stated overwrite behavior ('which deletes the existing file first'), so no contradiction. The description adds substantial behavioral detail beyond the annotation: error-on-existing-file unless overwrite=True, format determined by REAPER's last render settings, and the rationale that REAPER's overwrite prompt blocks unattended rendering. This is context the annotation alone cannot convey.

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?

Front-loaded with the core purpose, followed by a behavior note, then a clean Args section, then Returns. The overwrite rationale is somewhat verbose but earns its place because it explains non-obvious behavior that would otherwise confuse an agent invoking the tool unattended. Every section serves a purpose.

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?

All five parameters, the format behavior, and the overwrite semantics are covered, leaving little ambiguity about how to call the tool. The one gap is the Returns statement—'Object with render status and REAPER's computed output target(s)'—which lacks field-level detail, and with no output schema available, the agent must guess the return structure. Minor but real.

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 fully compensate, and it does. Every parameter (output_path, start_time, end_time, tail_seconds, overwrite) has a dedicated line with type semantics and defaults ('None = project start'). This exceeds the minimum expected from a bare schema that supplies only types and defaults.

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 first sentence states a specific verb and resource: 'Render the project's master mix to an audio file.' This is unambiguous and immediately distinct from the sibling render_region, which targets a region rather than the entire master mix. The purpose requires no inference.

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 strong context for the tool itself (format selection via extension, time-range semantics, overwrite handling) but offers no explicit differentiation from the closely related sibling render_region. No 'when not to use' or alternative-routing guidance is present, so usage boundaries are implied rather than stated.

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