list_track_templates

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

With no annotations, the description carries the burden and largely meets it: it discloses that the scan is recursive into subfolders and enumerates the exact shape of each entry ('name', 'path' relative form with an example, absolute 'file', contained track names). It doesn't mention cost, failure modes (e.g. missing folder), or ordering, which keeps it from a 5.

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?

Three sentences, front-loaded with the verb and resource, then the entry fields, then the downstream handoff. Every clause earns its place, and the 'Vocals/Lead Vox' example is a compact way to convey path format.

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?

There is no output schema, so the description must describe the return values, and it does so field by field including the relative-vs-absolute path distinction. Combined with the insert_track_template pointer, an agent has everything needed to call it and act on the result.

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?

Zero parameters, so baseline is 4; the description correctly adds nothing about inputs and instead spends its words on output field semantics. That is useful given the empty schema, though it belongs more to return-value clarity than parameter meaning.

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+resource ('List the track templates') and pins down the location (.RTrackTemplate files in REAPER's TrackTemplates folder, subfolders included), which distinguishes it from sibling list_tracks and from insert_track_template. The scope of entries returned is spelled out so an agent knows exactly what it gets.

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?

"Pass either 'name' or 'path' to insert_track_template" tells the agent this is the discovery step preceding insertion, which is real routing guidance to a named sibling. It stops short of explicit when-not-to-use guidance or stating whether it is safe/idempotent, but the intended workflow is unambiguous.

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