batch_export_regions

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

With no annotations, the description carries the full burden. It usefully discloses that the tool reuses the project's configured format and only swaps bounds, output directory, and pattern, which is genuine behavioral context. It says nothing about overwrite behavior, whether files are created vs replaced, permissions, or what the call returns.

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 tightly packed sentences with the core action front-loaded and no filler. The format/wildcard details follow naturally. Slightly dense parenthetical in sentence two, but nothing is wasted.

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 write-side tool with no annotations, no output schema, and zero schema description coverage, the description should cover more ground. It handles the format-routing question well but leaves 'only_matching', overwrite semantics, and failure modes unexplained.

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 does so only partially. It explains file_name_pattern well (REAPER wildcards, default '$region' meaning filename equals region name) and implies output_dir, but 'only_matching' is never mentioned anywhere in the schema or description.

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 with explicit scope: 'Render every region in the project to its own file.' The 'every region' framing implicitly separates it from the single-item render siblings, but no sibling is named, so the differentiation is left to inference rather than stated.

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?

Provides one real prerequisite: the render FORMAT must be configured once in REAPER's Render dialog beforehand. However, it never says when to pick this over render, render_with_current_settings, or batch_rename_regions, so the agent must guess the boundary between batch region export and a normal render.

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