compose_jazz_generative

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

With no annotations, the description carries the full behavioral disclosure burden. It richly explains what the tool will generate: bass feel changes, drum comping behavior, ensemble dynamics, and phrase-level details. However, it does not disclose project-level effects such as whether a new track is added or an existing composition is replaced.

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 a single dense sentence with no filler, and every clause contributes meaningful musical direction. It is slightly run-on and could be broken into structured points for readability, but it remains efficient.

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-argument generative tool, the description gives enough detail about output style, instrumentation, and arrangement for an agent to invoke it correctly. The only notable gap is that it does not state what happens to the current project state or what return/confirmation the agent should expect.

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 has zero parameters, so there are no parameter semantics for the description to clarify. The detailed musical description effectively serves as the tool's configuration context, which is appropriate for a no-argument generative tool.

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 uses a specific verb ('Generate'), names the resource ('jazz/jaunty track'), and gives concrete distinguishing details such as walking bass, Rhodes comping, and vocal-treated piano lead. This clearly separates it from sibling generative tools like compose_lofi_generative and compose_synthwave_generative.

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 'jazz/jaunty' style label and the detailed musical vocabulary make the intended use case clear, and the description implies this tool is for jazz-style generation rather than other genres. It does not explicitly state when-not-to-use or name alternatives, so it stops short of a 5.

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