reaper_render_project

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

Annotations provide readOnlyHint (false), destructiveHint (false), idempotentHint (false), and openWorldHint (true). The description expands on these by stating the tool reuses previous settings (no parameters needed) and that it writes a file but does not modify the project, which aligns with the annotations and adds valuable detail about side effects.

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?

Two sentences efficiently convey the tool's function, prerequisites, and effect. No unnecessary words or repetition.

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 zero-parameter tool with no output schema, the description fully covers what the agent needs to know: what it does, its prerequisites, and its side effects. The contextual signals confirm the simplicity, so the description is complete.

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?

The tool has zero parameters, so the baseline is 4. The description adds value by explaining why there are no parameters (reuses previous settings), which compensates for the lack of schema detail.

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 clearly states the tool renders a project to disk using Reaper's last render settings, with specific mention of output path, bounds, and format. This distinguishes it from all sibling tools, none of which perform rendering.

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 explicitly instructs users to set up render settings manually first, providing crucial context. It also clarifies that the tool writes a file without modifying the project, helping agents understand when to use it. No direct alternative is mentioned, but no sibling tool serves the same purpose.

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