postfader_render_saved_project

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

Annotations already indicate this is not read-only, but the description adds meaningful behavioral context: it launches a separate process, implying asynchronous execution, and uses only the saved project state. It does not cover details like file overwrite behavior or concurrent jobs, but there is no contradiction with the annotations.

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?

One compact sentence front-loads the verb and resource, and the 'saved state only' qualifier earns its place as an important constraint. There is no redundant or filler phrasing.

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?

Given that an output schema exists and sibling tools handle job inspection and cancellation, the description covers the critical launch semantics: separate process and saved-state-only input. It does not explain timeout behavior or FL Studio path discovery, but those are represented in the schema defaults, so the remaining gaps are minor.

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 100%, and the nested request schema already documents project_path, output_directory, fl_studio_path, and timeout_seconds. The tool description adds only the high-level 'saved state only' constraint; the request schema already describes the inputs as a saved .flp and parent output directory, so the description contributes little beyond structured data.

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 action and resource: 'Start FL's command-line WAV exporter in a separate process.' The qualifier 'saved state only' plus the annotation title 'Render a saved FL Studio project' makes the tool's scope clear and distinguishes it from generic postfader execution or live-state operations.

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 phrase 'saved state only' implies the key precondition: the project must be saved before calling and unsaved changes will not be rendered. However, the description does not explicitly name alternatives or state when not to use this tool, so routing among sibling render/execute tools still depends mostly on the tool name.

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