transport_pause

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

With no annotations provided, the description carries the full burden but fails to disclose critical behavioral traits: whether this is stateful (toggles between pause/play), what happens to the cursor/playback position when paused, or whether it can be invoked when already paused. 'Toggle' implies bidirectional behavior but lacks specifics.

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?

Extremely concise at six words with zero redundancy. The single sentence front-loads the action ('Toggle pause') and immediately qualifies the context ('during playback or recording'), earning its place efficiently.

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 zero-parameter transport tool without output schema, the description identifies the core function adequately. However, it lacks behavioral nuance (toggle semantics, state prerequisites) that would be necessary for an agent to predict side effects or error conditions.

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 input schema contains zero parameters (empty properties object), establishing baseline 4 per evaluation rules. No parameter semantic information is required or provided in the description, which is appropriate for a simple transport control.

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 uses specific verbs ('Toggle pause') and identifies the resource context ('playback or recording'), distinguishing it from sibling transport controls like transport_play or transport_stop. However, it leaves ambiguity whether this exclusively pauses or also resumes playback.

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 provided on when to use this versus transport_stop (which keeps vs resets position) or how it interacts with transport_play for resuming. The agent cannot determine if this is the correct tool for temporarily halting versus stopping completely.

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