select_all_tracks

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

Annotations only include destructiveHint: false, which is minimal. The description adds no further behavioral context—no mention of side effects, selection state changes, or requirements. The tool likely mutates selection, but the description is silent on this, leaving the agent to infer 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 a single, concise sentence with zero filler. It is front-loaded and immediately comprehensible, achieving maximal efficiency for a zero-parameter action.

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 simple zero-parameter selection action with no output schema, the description is largely sufficient. It clearly states the target (all tracks) and the action. The only gap is lack of mention of selection state replacement, but this is minor given the low complexity and common DAW behavior.

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 tool has zero parameters, and schema coverage is trivially 100% (empty schema). Baseline for 0 params is 4. The description's 'all' clarifies scope (selects all tracks rather than a subset), which adds minor semantic meaning beyond the tool name, but no parameter details are needed.

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 'Select all tracks' clearly states the action and resource with a specific verb ('Select') and object ('all tracks'). It distinguishes from obvious siblings like 'unselect_all_tracks' by the explicit 'all' and 'select'. However, it doesn't explicitly differentiate from 'select_track' (singular), but the 'all' modifier provides enough distinction.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives like 'select_track', 'get_selected_tracks', or 'unselect_all_tracks'. There's no mention of selection state behavior (e.g., whether it clears existing selection), so the agent lacks context for appropriate invocation.

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