Resume Playback

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

The description adds the 'if paused' condition, which is not in annotations. Annotations already provide idempotentHint=true and destructiveHint=false, so the behavior is safe, but the description does not clarify what happens if invoked while already playing (e.g., no-op vs error).

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 extremely concise at 5 words, front-loaded with the action and condition, with no wasted words.

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 simple tool with no parameters and no output schema, the description covers the basic function. However, it could be more complete by describing the result (e.g., returns nothing or indicates success) and the behavior when not paused.

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 no parameters and schema coverage is 100%, so the description does not need to add parameter meaning. The 0-param baseline is 4 per rubric.

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 'Resume playback if paused.' clearly states the tool's action (resume) and resource (playback), and the conditional phrase distinguishes it from sibling tools like mpv_pause and mpv_stop.

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 implies when to use the tool (when playback is paused), but it does not explicitly state when not to use it or mention alternative tools like mpv_play, which might also resume playback.

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