render

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

The description discloses two important behavioral traits: 'No undo' and 'Long timeout'. However, with no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention that rendering is a potentially expensive or blocking operation, whether it overwrites files, what happens on failure, or whether it requires specific project state. The 'No undo' warning is useful but incomplete.

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 very short and front-loaded with the key warning ('No undo') and the bounds enum. Every phrase carries some information, but the structure is telegraphic and could be clearer. It is concise but not well-structured enough to be a model of clarity.

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 9 parameters, 0% schema coverage, no annotations, and no output schema, the description is far from complete. It does not explain the return value, the effect of each parameter, or the rendering workflow. The 'No undo' and 'Long timeout' warnings are valuable, but an agent would still be guessing about most parameters and the overall behavior.

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 for the 9 undocumented parameters. It only explains 'stems' and 'track_indices' partially, and lists 'bounds' enum values without explaining their meaning. Parameters like 'pattern', 'channels', 'end_beats', 'sample_rate', and 'start_beats' are completely unexplained. The description adds some value for stems/track_indices but leaves most parameters ambiguous.

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 starts with 'Render' as a verb, which identifies the core action, and lists the bounds enum values. However, it does not explicitly state what 'render' produces (e.g., audio file export) or what resource it operates on beyond the bounds options. It is distinguishable from siblings like 'transport' or 'midi' but not clearly differentiated from a generic render operation.

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 gives a brief hint about stems=true and track_indices, but it does not explain when to use this tool versus alternatives like 'batch' or 'run_lua'. There is no mention of prerequisites, typical use cases, or when not to use it. The guidance is minimal and mostly assumes the agent already knows when rendering is appropriate.

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