garageband_select_track

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

With no annotations provided, the description must fully disclose behavioral traits. It states 'select a visible track' but omits details on failure modes (invalid index/name), state changes, or interaction with parameters like max_depth, x_offset, etc. The tool's behavior under edge cases is not explained.

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 sentence that efficiently conveys the core purpose and effect. It is front-loaded with the action and object. However, it could be more structured by breaking into multiple sentences for clarity.

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?

Given 7 parameters with complex defaults and no output schema, the description is incomplete. It does not explain the purpose of technical parameters, nor behavior when multiple tracks match. The tool's full functionality is not adequately documented.

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 add meaning. It mentions index and name, but does not explain format, constraints, or the other 5 parameters (max_depth, x_offset, y_fraction, fast, row_height). This is insufficient to guide correct parameter usage.

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 clearly states the verb 'select', the resource 'visible GarageBand track', and the method 'by index or visible name'. It also explains the downstream effect on Library and Smart Controls. However, it does not differentiate from the sibling tool 'garageband_set_track', leaving slight ambiguity.

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 guidance on when to use this tool versus alternatives like 'garageband_set_track'. The description implies usage when needing to act on a track via Library/Smart Controls, but fails to provide when-not-to-use or identify prerequisites.

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