audio_focus_next_playlist

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. 'Focus' implies a state change, but it doesn't disclose whether this is a read-only operation, what 'focus' entails (e.g., activates playback, selects for editing), side effects, or error conditions. It lacks context on permissions, rate limits, or system impact.

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, efficient sentence with no wasted words. It's front-loaded with the core action ('Focus the next audio playlist'), making it easy to parse. Every word earns its place by conveying the essential purpose.

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 no annotations, no output schema, and a potentially state-changing operation ('focus'), the description is incomplete. It doesn't explain what 'focus' does, what happens if no 'next' playlist exists, or what the tool returns. For a tool in a complex media-control context with many siblings, more behavioral detail is needed.

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 with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add param info, but that's appropriate here. Baseline is 4 for zero-param tools, as the schema fully covers the absence of inputs.

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 'Focus the next audio playlist' clearly states the verb ('Focus') and resource ('next audio playlist'), but it's vague about what 'focus' means operationally. It distinguishes from siblings like 'audio_focus_previous_playlist' by direction, but doesn't clarify how it differs from 'audio_focus_playlist' or 'audio_focus_active_playlist' beyond the 'next' qualifier.

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 guidance is provided on when to use this tool versus alternatives. It doesn't specify prerequisites (e.g., requires an existing playlist), exclusions, or compare to siblings like 'audio_focus_active_playlist' or 'audio_focus_playlist'. The agent must infer usage from the name alone.

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