transport_stop

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

With no annotations, the description carries the behavioral disclosure burden and does state the primary effect: playback is halted. It does not mention whether the cursor position is preserved, whether the call is a no-op when not playing, or any other side effects.

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 two words and exactly captures the operation with no filler or repetition. Every part earns its place.

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 action, this covers the basic invocation and intent. It is not fully complete because it leaves the sibling distinction and behavioral details unarticulated, which matter in a large tool set with transport_play_stop nearby.

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 confirms this, so there are no parameter semantics to explain. The description does not need to add anything beyond the input schema for an agent to invoke it correctly.

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 a specific verb ('Stop') and a clear resource ('playback'), so an agent can tell what action is performed. It does not explicitly contrast with the sibling transport_play_stop, so the sibling differentiation is weaker than ideal.

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?

'Stop playback' implies the tool should be used when playback needs to be halted. However, it gives no explicit guidance about when not to use it or why it should be preferred over the similar-sounding transport_play_stop.

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