render_backing

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the output formats and one default, but says nothing about where files are written, whether existing files are overwritten, naming behavior, or anything about a process that writes two files to disk.

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 short sentences, front-loaded with the action and output, then the one default worth calling out. No filler and every clause carries information.

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 an 11-parameter, side-effect-producing tool with no annotations and no output schema, the description covers a small slice. It never explains the resulting files' location or how the many musical options shape the render, leaving the agent under-informed for correct invocation.

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% across 11 parameters. The description clarifies only one of them — that 'bars' defaults to one pass through the progression (a meaning the null default does not convey). The remaining ten parameters (style, tempo, instrument, soundfont, drums, bass, output_dir, etc.) receive no elaboration anywhere.

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 verb (render) and resource (backing track from a chord progression) plus the output artifacts (.mid and .wav). The word 'only' weakly signals contrast with a fuller-song render, but no sibling is named, so differentiation from create_song is left to inference.

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?

There is no explicit when-to-use guidance and no alternatives are named. The adverb 'only' implies a contrast with other render paths, but the agent must guess which sibling to prefer and under what conditions.

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