transport_stop

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it only restates the obvious side effect of stopping. It does not disclose whether the playhead position is preserved or reset, whether recording is also stopped, whether the command is idempotent, or what transport_status would report afterward.

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?

Two words with zero waste; the action is front-loaded and entirely on point. For a zero-parameter tool this is an appropriately minimal description.

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 trivial complexity (no params, no output schema), the description covers the core action adequately. It is missing small but useful context that an agent would need to reason about side effects, such as whether stop applies to recording and what happens to the playback position, and it does not reference related transport_status for verification.

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 zero parameters and the schema is empty, so there is nothing for the description to explain. The baseline of 4 applies since no parameter semantics are needed.

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 states a specific verb ('Stop') and resource ('playback'), making the core action unambiguous. It is self-differentiating from obvious siblings like transport_play and transport_record, though it does not explicitly clarify whether it also halts an active recording.

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?

Usage is implied rather than stated: an agent can infer this tool is used when playback should be halted. However, there is no explicit guidance on when not to use it (e.g., for pausing, toggling, or stopping a recording) and no named alternatives.

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