get_track

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds useful behavioral detail about what is returned and how detail=True expands the result to every slot, arrangement clip, full mixer, meters, and flags.

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 and front-loaded, with the core read behavior first and detail-mode behavior second. The final track-format line is slightly orphaned but still useful, and there is no filler.

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?

With no output schema and zero schema parameter descriptions, the definition adequately explains the returned track contents, the detail flag, and accepted track identifiers. It omits error behavior and exact response shape, but for a read-only inspection tool it is largely complete.

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 carry all parameter meaning. It does: track accepts an index, name, "return:A", or "master", and detail=True is explicitly defined as expanding the response to include everything else.

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 opens with a specific verb and resource: 'Read one track'. It then enumerates the exact content returned (mixer, routing, devices, session slots, arrangement, take lanes), which makes it clearly distinct from sibling tools like get_mixer, get_devices, or get_song_overview.

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 implies when to use the tool by defining it as a single-track read and explains how the detail flag changes scope. However, it does not explicitly compare against alternatives such as get_mixer, get_devices, or get_song_overview, so routing between siblings remains inferred.

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