raw_next_track

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 partially does this by warning that the action 'may open a dialog or change project state' and by noting it is static and no-argument. However, the warning is vague, does not specify what could change or why, and does not clarify the return or side-effect profile beyond a generic caveat.

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 concise and front-loaded: purpose first, then action characteristics, then a caution. It contains no filler, though the final clause 'inspect the command name first' is cryptic and could be clearer without adding much length.

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 no-argument tool, the description covers the core purpose, argument count, and potential side effects. However, it leaves ambiguity about what 'inspect the command name first' means and about exactly what state changes or dialogs may occur. An agent could call the tool, but it cannot fully predict the outcome or prerequisites.

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 schema has zero parameters and 100% schema description coverage, so no parameter documentation is required. The description reinforces this by explicitly stating 'no-argument,' which is helpful confirmation. This matches the baseline for a zero-parameter tool.

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 action and resource: 'Focus the next track.' It also identifies this as a static no-argument Audacity action, and the word 'next' distinguishes it from sibling commands like raw_prev_track, raw_first_track, and raw_last_track.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention raw_prev_track, raw_first_track, or any routing condition. The instruction to 'inspect the command name first' is not a practical usage guideline and leaves the agent without clear selection criteria.

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