transport_pause

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the key behavior—toggling pause—and restricts it to playback or recording contexts. However, it does not explain what happens when transport is already paused, stopped, or inactive, leaving some behavioral ambiguity.

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 compact sentence that front-loads the action ('Toggle pause') and immediately states the applicable contexts ('during playback or recording'). Every word earns its place; there is no redundant or vague filler.

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-parameter transport toggle, this is minimally adequate, but it leaves out edge-case behavior: what occurs when transport is stopped, whether toggling applies to playback and recording independently or together, and whether position is preserved. With no annotations and no output schema, those gaps are not compensated elsewhere.

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?

This tool has zero parameters, so there is nothing for the description to add beyond the schema. The baseline for a no-parameter tool is 4; no parameter documentation is necessary.

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 specifies a concrete transport action—toggle pause—and explicitly scopes it to playback or recording. It is clear enough to be distinguished from sibling tools like transport_play, transport_stop, and transport_record, though the exact state transition (whether it always resumes or only enters pause) is implied rather than stated.

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 given about when to use this tool versus alternatives such as transport_play, transport_stop, or raw_play_stop. The description does not mention whether the tool is only meaningful while transport is active, nor does it indicate any conditions or exclusions.

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