select_none

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the main behavior — deselecting all audio — but adds no extra context such as whether the action is undoable or scoped to the current project. For a zero-parameter action, this is minimally suficient but not rich.

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 declarative sentence with no wasted words. The action verb is front-loaded and every word contributes to the meaning.

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 zero-parameter tool with no output schema, the description is largely complete: it identifies the action and scope. It could nominally mention it applies to the current project or clears selected audio across all tracks, but 'Deselect all audio' conveys the necessary information to invoke the tool correctly.

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 accepts zero parameters, and the input schema already reflects this with an empty properties object. Since there are no parameters to describe, the baseline for zero-parameter tools applies and the description does not need to add parameter-specific 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?

The description 'Deselect all audio.' uses a specific verb (deselect) and a clear resource (all audio), fully stating the tool's effect. It distinguishes itself from sibling selection tools like select_all and select_region without needing to open their schemas.

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 intended usage is implied: call this when you want to clear the current selection across the project. However, the description does not explicitely say when to use it vs. alternatives or provide any context about prerequisites or exclusions. It's inferable from the name but not articulated.

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