render

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the dependency on REAPER's current render format and how to configure it, plus the meaning of the bounds options. However, it says nothing about whether existing files are overwritten, whether the operation blocks, or what success/failure looks like for a write-to-disk operation.

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 tight sentences, front-loaded with the action and then the parameter specifics. Dense with useful detail and no filler; the parenthetical about format configuration 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?

For a disk-writing render operation with no annotations and no output schema, the description covers bounds and naming well but omits overwrite behavior, `sample_rate` semantics, and any return/result signal. Adequate but with clear gaps given the tool's weight.

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 0%, so the description must compensate, and it largely does: it enumerates the valid `bounds` values (the schema provides no enum, only a default) and documents the wildcard syntax for `file_name_pattern` with concrete examples. It leaves `sample_rate` (and the semantics of `output_dir` creation) unexplained, so it's not exhaustive.

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?

Specific verb+resource: renders a project to a directory with given bounds and file pattern. The description names the render domain precisely and even distinguishes itself somewhat from `render_with_current_settings` by explaining where the extension/format comes from. It does not explicitly position itself against siblings like `batch_export_regions`, so it's clear but not fully sibling-differentiated.

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 hints at the format-config workflow ('configure via REAPER once, or call `render_with_current_settings`'), which is useful routing context. But it never states when to choose `render` over `batch_export_regions` or `render_with_current_settings` directly, nor when each `bounds` value is appropriate. Usage is implied rather than directed.

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