select_none

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

No annotations are provided, so the description carries the full burden. It states the action but does not clarify behavioral traits like whether this affects all tracks vs current track, if it requires an open project, or that it is non-destructive (merely changing selection state). For a state-change tool, this is minimally adequate but lacks safety context.

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 three words: 'Deselect all audio.' It is maximally concise with zero redundancy, front-loaded with the action verb, and contains no wasted text.

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 the low complexity (0 parameters, no output schema, simple selection operation), the description is sufficient. However, it could be improved by clarifying scope (e.g., 'across all tracks' or 'in the current project') to match the granularity of sibling select_* tools.

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 0 parameters, which establishes a baseline of 4. With no parameters to describe, there is nothing to add, and the schema coverage is 100% (trivially).

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 uses a specific verb ('Deselect') and resource ('audio'), clearly distinguishing it from siblings like select_all (opposite operation), select_clip (specific item), and select_region (specific range). The scope ('all') is explicitly stated.

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?

While the tool's purpose is clear from the name and description, there are no explicit guidelines on when to use this versus alternatives (e.g., 'use this to clear selection before applying effects to specific tracks only') or prerequisites. Usage is implied but not stated.

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