continue_playing

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

The annotation shows destructiveHint=false, and the description confirms non-destructive behavior by stating 'resume playback.' It also adds specific detail about the playhead position, going beyond the annotation to explain the exact 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, efficient sentence with a parenthetical clarification, front-loading the core purpose. Every word adds value.

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 tool has no parameters and an output schema exists, the description completely explains its action (resume playback) and distinguishes it from a sibling. No further context 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?

With zero parameters, the schema coverage is 100%, so the baseline is 4. The description does not need to add parameter information, and the tool's behavior is fully conveyed.

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 'Resume playback from the current position' and distinguishes from the sibling tool 'start_playback' which 'restarts from the playhead's last start point instead.' It uses a specific verb and resource, making the purpose unambiguous.

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 explicitly contrasts with 'start_playback' to guide when to use this tool (resume vs. restart). It provides clear context but does not elaborate on other situations where it might be inappropriate.

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