render_regions

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

With no annotations provided, the description carries the full burden and does so well: it discloses file creation, temporary render-setting changes in dry_run, refusal to overwrite existing files, no deletion behavior, blocking until completion, and the complete/stalled/timeout statuses. The stall detection condition is also explained clearly.

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 description is front-loaded with the core action and then organized around parameter names and behavioral conditions. It is dense but every sentence adds useful operational detail, and the length is justified for a six-parameter tool with no annotations.

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 tool with no annotations and no output schema, the description covers most behavioral and failure semantics thoroughly, including dry_run returns and final status values. The main gap is that the required output_directory parameter is not described, leaving the destination semantics partially implicit.

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. It explains pattern variables and collision numbering, selected_only behavior, dry_run behavior, and both timeout-related parameters, but it never explains the required output_directory parameter.

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 description gives a specific verb, resource, and scope: render each project region to its own file using project render settings. That scope implicitly distinguishes it from whole-project, stem, and time-selection renders without ambiguity.

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 clearly explains when selected_only applies and what dry_run does, including the failure behavior when output files already exist. It does not explicitly name sibling alternatives such as render_project or render_stems, so selection guidance is strong but not fully comparative.

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