render_project

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

With no annotations provided, the description carries the full behavioral burden. It discloses that LMMS runs in headless mode without GUI, that the project is saved before rendering, and that an external LMMS installation is required. It could also mention output file overwrite behavior, but the disclosed side effects and prerequisites are already substantive.

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 purpose in the first sentence, followed by a compact behavioral note and a clear Args list. Every sentence provides useful information, with no filler 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 4-parameter tool with no annotations, the description covers the key contextual needs: external dependency, headless behavior, save-first side effect, and complete parameter semantics. An output schema exists, so return-value details are not required. Minor omissions like overwrite behavior do not undermine usability.

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 input schema only provides titles and defaults with no descriptions, so the Args section adds essential meaning: allowed file_format values, samplerate units in Hz, bitrate purpose for lossy formats, and the output_path default behavior of <project>.wav in the same directory. This fully compensates for the 0% schema description coverage.

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 states a specific verb and resource: 'Export the current project to an audio file.' This clearly distinguishes render_project from siblings like save_project or get_project_info, and there is no other export/render tool in the sibling list.

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 intended use case is clear: export the current project to an audio file via LMMS. It mentions prerequisites ('Requires a working LMMS installation') but does not explicitly name alternatives or exclusion conditions. Since no sibling tool overlaps with rendering to audio, the absence of explicit alternatives is acceptable.

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