compose_djent_real

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

With no annotations, the description carries the full behavioral burden. It discloses a critical manual requirement (loading the SFZ in sforzando once), explains why (state not preserved in the .tracktionedit writer), and states that the tool returns a manual_step_required note. This is strong transparency for a compose tool, though it does not mention side effects or output file behavior.

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 dense but efficient: both sentences earn their place, with the real-instrument distinction and signal chain front-loaded and the manual step explained immediately after. Slightly long due to the detailed chain, but no wasted words.

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?

The description covers the core purpose and the essential manual caveat, but with no output schema and no annotations, it leaves the required out_path parameter unexplained and does not state what the tool ultimately writes or returns beyond the manual_step_required note. Adequate for a specialized compose tool, but incomplete for fully reliable 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%, so the description must compensate for the undocumented seed, tempo, and out_path parameters. It provides no parameter-level guidance at all, not even clarifying what out_path should point to. This is a significant gap.

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 names a specific verb and resource ('Djent track using REAL VST3 instruments + amp/cab simulators') and explicitly contrasts with 'synthetic 4OSC', distinguishing it from the sibling compose_djent_track. The signal chain is concrete enough that an agent knows exactly what this tool produces.

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 'instead of synthetic 4OSC' phrase gives clear context for when to choose this tool over a synthetic composition path. It does not explicitly name sibling tools or provide when-not-to-use guidance, but the real-versus-synthetic distinction is an effective selection cue.

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